-
-
Notifications
You must be signed in to change notification settings - Fork 952
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make development easier #11547
Comments
This issue has been automatically marked as stale because there wasn’t any recent activity. It will be closed soon if no further action occurs. Thank you for your contributions! |
Mhmm also the default |
Any ideas? |
I had to manually setup the DB. Ideally the dev setup should be zero config, so we can enable the people CREATE USER weblate;
ALTER USER weblate WITH PASSWORD 'weblate';
GRANT USAGE ON SCHEMA public TO weblate;
CREATE DATABASE weblate;
ALTER DATABASE weblate OWNER TO weblate; |
This really should be done by the PostgreSQL container during the initial startup. You can check its logs why it didn't. It is supposed to be zero config, and we do verify that in CI: https://github.com/WeblateOrg/weblate/blob/main/.github/workflows/rundev.yml |
Describe the problem
While trying to setup the development environment to tackle #11467, I noticed how difficult it is to setup the environment.
I ran into my dependency problems, as we don't have a dependency manager here so a virtualenv needs to be used with a specified version of Python.
And now I'm stuck on this issue, while running
weblate migrate
. I have no idea why it tries to open an LDAP connection on migrate. I'm familiar with Django setups, but this is a bit different.Then I thought, maybe let's just use the docker-compose setup for a simple fix and there I need to create
docker-compose.override.yml
.I think this project would benefit from a zero-setup start just to develop it.
Describe the solution you would like
a zero-config setup development environment
Describe alternatives you have considered
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: