Configuration of Production Server #3

Closed
opened 2023-02-08 12:12:26 +01:00 by Francesco Siddi · 1 comment

This task is a bit of a scratch-pad for us to remember certain configuration options.

  • [service] AUTO_WATCH_NEW_REPOS = false
    • To avoid org members to become watcher on newly created repositories.
  • [attachment] MAX_SIZE = 500 (500MB) (#41)
  • [ui] ISSUE_PAGING_NUM = 50 (#41)
  • [repository] MAX_CREATION_LIMIT seems to be incorrectly set to 1?
    • Should allow creating multiple repositories in any case. Not sure how many, at least 10.
  • [packages] ENABLED = false
  • [attachment] ALLOWED_TYPES = */*
    • Allow updating all file types, since it's difficult to get a complete list of all relevant ones.
  • Domain for git repositories? (#50)
  • Search in issues is not working on projects.blender.org
  • Ensure http:// redirects to https:// to avoid warning
  • Enable lfs (https://docs.gitea.io/en-us/git-lfs-setup/)
    • Not immediately required for existing repos, but will be used in the future
  • [ui] THEMES = bthree-dark,~~auto~~,gitea,~~arc-green~~
    • The existing themes work, and a light theme can be important for usability for some people.
  • [webhook] ALLOWED_HOST_LIST = 192.168.2.5
  • [repository] DISABLE_MIGRATIONS = true
    • This was marked done but the migration button is still there, check if this was done?
  • [repository.pull-request] ADD_CO_COMMITTER_TRAILERS = false
    • Otherwise squash merge always adds co-authored regardless if the person merging changed anything
    • Also related to this: #41

After migration:

  • Enable searches to work without index-engine 'db'
  • Disable HTTPS push with password, should require SSH key
  • Consider enabling code search (once we are confident existing server has good performance)
    • May need to do something to disable it in forks? Or is it smart enough to do the work only once?

Originally created by Sybren.

This task is a bit of a scratch-pad for us to remember certain configuration options. - [x] `[service] AUTO_WATCH_NEW_REPOS = false` - To avoid org members to become watcher on newly created repositories. - [x] `[attachment] MAX_SIZE = 500` (500MB) (#41) - [x] `[ui] ISSUE_PAGING_NUM = 50` (#41) - [x] `[repository] MAX_CREATION_LIMIT` seems to be incorrectly set to 1? - Should allow creating multiple repositories in any case. Not sure how many, at least 10. - [x] `[packages] ENABLED = false` - [x] `[attachment] ALLOWED_TYPES = */*` - Allow updating all file types, since it's difficult to get a complete list of all relevant ones. - [x] Domain for git repositories? (#50) - [x] Search in issues is not working on projects.blender.org - [x] Ensure http:// redirects to https:// to avoid warning - [x] Enable lfs (https://docs.gitea.io/en-us/git-lfs-setup/) - Not immediately required for existing repos, but will be used in the future - [x] `[ui] THEMES = bthree-dark,~~auto~~,gitea,~~arc-green~~` - The existing themes work, and a light theme can be important for usability for some people. - [x] `[webhook] ALLOWED_HOST_LIST = 192.168.2.5` - [x] `[repository] DISABLE_MIGRATIONS = true` - This was marked done but the migration button is still there, check if this was done? - [x] `[repository.pull-request] ADD_CO_COMMITTER_TRAILERS = false` - Otherwise squash merge always adds co-authored regardless if the person merging changed anything - Also related to this: #41 After migration: - [x] Enable searches to work without index-engine 'db' - [ ] Disable HTTPS push with password, should require SSH key - [ ] Consider enabling code search (once we are confident existing server has good performance) - May need to do something to disable it in forks? Or is it smart enough to do the work only once? Originally created by Sybren.
Brecht Van Lommel added the
Type
Deployment
label 2023-02-08 18:22:50 +01:00
Arnd Marijnissen was assigned by Brecht Van Lommel 2023-02-09 12:23:43 +01:00

Moved https-login to #30 and codesearch to #31

Moved https-login to #30 and codesearch to #31
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/blender-projects-platform#3
No description provided.