Skip to content
Riccardo Graziosi edited this page Jan 9, 2020 · 4 revisions

If you could not find help here, consider opening an issue.

During run and update scripts

Yarn warnings

During the update process you may get some yarn warnings like: warning <module> has unmet peer dependency <module>. This is a known issue and hopefully will be fixed soon, but nonetheless Astuto will run fine.

Database authentication failed

You probably changed POSTGRES_USER and/or POSTGRES_PASSWORD after creating the database. You should do one of the following:

  • If you are good with the old credentials: set the two environment variables to their previous values.
  • If you want to keep the new credentials: manually provision postgres Docker container and change the credentials of the database.

Command "webpack-dev-server" not found

You probably changed ENVIRONMENT in your .env file and launched with script/docker-run.sh. Instead, you need to launch script/docker-update-and-run.sh.

standard_init_linux.go:211: exec user process caused "no such file or directory"

This is a known issue of Astuto on Windows. As of today there are no fixes for this problem. We do not have enough time to work on Windows support: if you are interested, you can contribute to Astuto to improve Windows support.

Miscellaneous

CSS and JS changes aren't picked up in production

When in production, after every change to a CSS or JS file, you must restart webpack (i.e. restart Astuto). If you want Astuto to pick up these changes automatically, you must run it in development.