twenty/.devcontainer/devcontainer.json


{
	"name": "Twenty Codespace",
	"image": "node:18.16.0",
	"features": {
	  "ghcr.io/devcontainers-contrib/features/jshint:2": {}
	},
	"forwardPorts": [3000, 3001, 5432],
	 "postCreateCommand": "cd front && yarn && cd ../server && yarn"
  }
I can open the project in GitHub (#92) * Ignore node_modules * Use bash-compatible dotenv format While still being compatible with dotenv, this also allows sourcing the file to export all variables in bash. * Add prettier extension to recommendations * Move to port 5001 to avoid conflict with macOS services * Add workspace * Add devcontainer This automatically starts with all environment variables available locally. It brings up services which are dependent on each other individually and verifies health before moving on to the next service. * Split init into clean, up, and logs tasks. This allows the developer to set up .env and .npmrc files before running services, and does not require starting from a clean db every time the devcontainer is restarted. * Copy .env when creating codespace * Automatically run UP command upon devcontainer creation * Fix log message --------- Co-authored-by: Felix Malfait <felix.malfait@gmail.com> 2023-05-03 12:34:10 +03:00
Simplify local dev (#137) 2023-05-25 16:56:28 +03:00			`{`
			`"name": "Twenty Codespace",`
			`"image": "node:18.16.0",`
I can open the project in GitHub (#92) * Ignore node_modules * Use bash-compatible dotenv format While still being compatible with dotenv, this also allows sourcing the file to export all variables in bash. * Add prettier extension to recommendations * Move to port 5001 to avoid conflict with macOS services * Add workspace * Add devcontainer This automatically starts with all environment variables available locally. It brings up services which are dependent on each other individually and verifies health before moving on to the next service. * Split init into clean, up, and logs tasks. This allows the developer to set up .env and .npmrc files before running services, and does not require starting from a clean db every time the devcontainer is restarted. * Copy .env when creating codespace * Automatically run UP command upon devcontainer creation * Fix log message --------- Co-authored-by: Felix Malfait <felix.malfait@gmail.com> 2023-05-03 12:34:10 +03:00			`"features": {`
Simplify local dev (#137) 2023-05-25 16:56:28 +03:00			`"ghcr.io/devcontainers-contrib/features/jshint:2": {}`
I can open the project in GitHub (#92) * Ignore node_modules * Use bash-compatible dotenv format While still being compatible with dotenv, this also allows sourcing the file to export all variables in bash. * Add prettier extension to recommendations * Move to port 5001 to avoid conflict with macOS services * Add workspace * Add devcontainer This automatically starts with all environment variables available locally. It brings up services which are dependent on each other individually and verifies health before moving on to the next service. * Split init into clean, up, and logs tasks. This allows the developer to set up .env and .npmrc files before running services, and does not require starting from a clean db every time the devcontainer is restarted. * Copy .env when creating codespace * Automatically run UP command upon devcontainer creation * Fix log message --------- Co-authored-by: Felix Malfait <felix.malfait@gmail.com> 2023-05-03 12:34:10 +03:00			`},`
Simplify local dev (#137) 2023-05-25 16:56:28 +03:00			`"forwardPorts": [3000, 3001, 5432],`
Add a custom rule to prevent colors from being hardcoded outside of theme (#288) * Add a custom rule to prevent colors from being hardcoded in ESLint * Refactor colors * Create packages folder and fix colors * Remove external dependency for css alphabetical order linting * Fix install with yarn --------- Co-authored-by: Charles Bochet <charles@twenty.com> 2023-06-14 17:56:29 +03:00			`"postCreateCommand": "cd front && yarn && cd ../server && yarn"`
Simplify local dev (#137) 2023-05-25 16:56:28 +03:00			`}`