2023-08-29 11:39:12 -07:00
|
|
|
// For format details, see https://aka.ms/devcontainer.json. For config options, see the
|
|
|
|
// README at: https://github.com/devcontainers/templates/tree/main/src/ruby-rails-postgres
|
|
|
|
{
|
|
|
|
"name": "Dress to Impress",
|
|
|
|
"dockerComposeFile": "docker-compose.yml",
|
|
|
|
"service": "app",
|
|
|
|
"workspaceFolder": "/workspaces/${localWorkspaceFolderBasename}",
|
|
|
|
"features": {
|
|
|
|
"ghcr.io/devcontainers/features/node:1": {
|
|
|
|
"nodeGypDependencies": true,
|
|
|
|
"version": "lts"
|
|
|
|
}
|
|
|
|
},
|
|
|
|
|
|
|
|
// Features to add to the dev container. More info: https://containers.dev/features.
|
|
|
|
// "features": {},
|
|
|
|
|
|
|
|
// Use 'forwardPorts' to make a list of ports inside the container available locally.
|
|
|
|
// This can be used to network with other containers or the host.
|
|
|
|
"forwardPorts": [3000],
|
|
|
|
|
|
|
|
// Use 'postCreateCommand' to run commands after the container is created.
|
|
|
|
"postCreateCommand": ".devcontainer/post-create.sh",
|
|
|
|
|
|
|
|
"containerEnv": {
|
Move the `host: db` part of the dev container into its environment vars
Okay, so I've kept `database.yml` using the new username and password
`impress_dev`, cuz I like that it helps clarify that it's dev stuff and
is impossible to confuse with prod. (I updated my local setup to match!)
But hardcoding `host: db` into here breaks my local setup where the
database _isn't_ at the hostname `db`. So I add a way for new optional
database URL environment variables to get merged in with these settings,
and then configured the dev container to use that—and just in the most
limited override possible, to avoid duplicating stuff we don't need to.
(I could've just used the same names `DATABASE_URL_{PRIMARY,OPENNEO_ID}`
for this, but idk, I think it's confusing to have the same one for both
dev and prod, even though Rails _does_ basically do this; see below.)
Normally, the environment variable `DATABASE_URL` just _does_ this, and
you don't need to include a `url` key at all to get this behavior. But
since we've got the legacy two-database thing going on, we do this
instead! If we were to merge the `openneo_id.users` table into the
primary database, we could simplify this!
2023-10-26 14:20:15 -07:00
|
|
|
// Because the database is hosted on the local network at the hostname `db`,
|
|
|
|
// we partially override `config/database.yml` to connect to `db`!
|
|
|
|
"DATABASE_URL_PRIMARY_DEV": "mysql2://db",
|
|
|
|
"DATABASE_URL_OPENNEO_ID_DEV": "mysql2://db",
|
2024-01-19 00:00:46 -08:00
|
|
|
"DATABASE_URL_PRIMARY_TEST": "mysql2://db",
|
|
|
|
"DATABASE_URL_OPENNEO_ID_TEST": "mysql2://db",
|
Move the `host: db` part of the dev container into its environment vars
Okay, so I've kept `database.yml` using the new username and password
`impress_dev`, cuz I like that it helps clarify that it's dev stuff and
is impossible to confuse with prod. (I updated my local setup to match!)
But hardcoding `host: db` into here breaks my local setup where the
database _isn't_ at the hostname `db`. So I add a way for new optional
database URL environment variables to get merged in with these settings,
and then configured the dev container to use that—and just in the most
limited override possible, to avoid duplicating stuff we don't need to.
(I could've just used the same names `DATABASE_URL_{PRIMARY,OPENNEO_ID}`
for this, but idk, I think it's confusing to have the same one for both
dev and prod, even though Rails _does_ basically do this; see below.)
Normally, the environment variable `DATABASE_URL` just _does_ this, and
you don't need to include a `url` key at all to get this behavior. But
since we've got the legacy two-database thing going on, we do this
instead! If we were to merge the `openneo_id.users` table into the
primary database, we could simplify this!
2023-10-26 14:20:15 -07:00
|
|
|
|
|
|
|
// HACK: Out of the box, this dev container doesn't allow installation to
|
|
|
|
// the default GEM_HOME, because of a weird thing going on with RVM.
|
|
|
|
// Instead, we set a custom GEM_HOME and GEM_PATH in our home directory!
|
|
|
|
// https://github.com/devcontainers/templates/issues/188
|
2023-08-29 11:39:12 -07:00
|
|
|
"GEM_HOME": "~/.rubygems",
|
|
|
|
"GEM_PATH": "~/.rubygems"
|
|
|
|
}
|
|
|
|
|
|
|
|
// Configure tool-specific properties.
|
|
|
|
// "customizations": {},
|
|
|
|
|
|
|
|
// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
|
|
|
|
// "remoteUser": "root"
|
|
|
|
}
|