Activity for Apache Allura™
-
Dave Brondsema modified a wiki page
Home
-
Dillon Walls committed [b76888]
8405 added last_access field to save the last access date for OAuth tokens
-
8405 updated API code samples from Python 2 to 3
-
OAuth Token Display Last Access Date
-
looks good. merged gc/8405
-
Guillermo Cruz committed [ea0118]
8405 updated API code samples from Python 2 to 3
-
Upgrade markdown
-
The ... setup-app ... command clears mongodb and sets up initial data, so you don't want to run that each time. I think you can just run docker-compose up -d after you set LOCAL_SHARED_DATA_ROOT. The ./allura-data/ directories should still contain the git repositories that you committed & pushed to, in case you need to recover that. But probably best to remove those directories and re-push any new commits (assuming your local checkout has the new commits still available to push again).
-
SF-6882 <hx> tag -> .hx-like
-
fixup! SF-6882 <hx> tag -> .hx-like
-
Make "enter" do the natural thing when adding an email to an account
-
peacecop kalmer: posted a comment on ticket #8406
Really, using git, the address worked, I could push and the data got pushed. After that, I rebooted the server machine and had to perform the following tasks in order to get allura running again: history 2002 cd /projektid/allura-git/Allura ... 2014 export LOCAL_SHARED_DATA_ROOT=./allura-data 2015 sudo -E sh -c 'docker-compose run taskd paster setup-app docker-dev.ini' ... 2022 docker-compose down 2023 docker-compose up -d The system is up again. However, there's another problem now: the pushed code...
-
Port 8080 is what you want everything to go through. When you have it set to 8080 and try to access the git repository, what logs show up in the 'http' container log? Also when you are trying the git URL, I wouldn't expect it to work in a browser. It provides git data, so it may only work with the git tool. Try git ls-remote http://allura.tennis24.ee/git/p/poster/puud.kalmer that actually works for me currently so you probably have it working right now!
-
Vrinda A posted a comment on ticket #8407
Thanks!. Finding all the models related to a project_id might need some time and effort to make sure nothing is missed out. Looking forward to your scripts to be open-sourced soon :)
-
In order to make it more comfortable for you to advice, I post some information. I did docker-compose logs and found these things for web_1 and http_1: web_1 | [2021-12-30 19:55:55 +0000] [9] [INFO] Starting gunicorn 20.1.0 web_1 | [2021-12-30 19:55:55 +0000] [9] [INFO] Listening at: http://0.0.0.0:8088 (9) web_1 | [2021-12-30 19:55:55 +0000] [9] [INFO] Using worker: sync web_1 | [2021-12-30 19:55:55 +0000] [12] [INFO] Booting worker with pid: 12 web_1 | 19:55:59,271 ERROR [tg.configuration.app_config]...
-
That URL looks right to me. I think you want to forward everything to port 8080 though. That port is the docker http server which handles git request as well as forwarding internally to 8088 for regular webpages. If that doesn't work still, I'd recommend looking at the docker-compose logs, specifically for the 'http' container (maybe 'web' too) and see if it has any clues.
-
For moving between instances, there is some closed-source scripts I have that backup, delete, and restore a project (optionally restoring with a new name). They have some parts I can't open-source immediately, but I can look into it. Conceptually they find all the models (mongo collections) that use the project_id and its app_config_id values. It dumps those as files. Then they can be restored back into the collection. One thing you can try exporting all your collections from mongo. Except users,...
-
Ingo posted a comment on ticket #8407
Very good point. I was also confronted with this requirement of moving projects a few times. In my case it was always within one instance for now. But the requirement is similar. Maybe there can be a way to serve all requirements!?... move between instances move between neighborhoods move from subproject (e.g. from the user profile) to a real one
-
Migration of project data
-
This time, I got allura up: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 94a4b1fae96d allura_web "paster taskd docker…" 10 seconds ago Up 5 seconds allura-git_taskd_1 b94e5553b729 allura-git_http "/usr/sbin/apache2 -…" 15 seconds ago Up 8 seconds 0.0.0.0:8080->80/tcp allura-git_http_1 dbd2fe548629 allura_web "python -u -m smtpd …" 16 seconds ago Up 10 seconds 8826/tcp allura-git_outmail_1 efc2af7d4421 allura-git_web "/bin/sh -c 'gunicor…" 21 seconds ago Up 15 seconds 0.0.0.0:8088->8088/tcp...
-
I haven't seen that error before, I think the 'web' container should be the only thing using that port. Maybe try docker-compose down and then docker-compose up -d to start the containers again? Otherwise there are several other possible fixes at https://stackoverflow.com/questions/46176584/docker-bind-for-0-0-0-04000-failed-port-is-already-allocated
-
I added these two lines suggested in the note 2. Thereafter, I did: docker-compose restart web as suggested and what I did get was: Restarting allura-git_web_1 ... error ERROR: for allura-git_web_1 b'Cannot restart container c12c96ff2d17ed189dc507ad278202c6c9678d4ac3bc85f7088e20cb8519c7ef: driver failed programming external connectivity on endpoint allura-git_web_1 (3163d2222fca567087b3c9db1758af36d0f3d6aaf54649de0230d83b5b6ad117): Bind for 0.0.0.0:8088 failed: port is already allocated' I wanted...
-
Ok good progress :) See note 2 at https://forge-allura.apache.org/docs/getting_started/installation.html#first-run That should help with different IP addresses
-
I added my user to docker's group and after that, only docker-compose build required sudo. This time, I reached further. After: docker-compose up -d I got: allura_mongo_1 is up-to-date allura_solr_1 is up-to-date allura_web_1 is up-to-date allura_outmail_1 is up-to-date Creating allura_inmail_1 ... done Creating allura_http_1 ... done Creating allura_taskd_1 ... done In the manual, I read: Visit localhost:8080, or on a Mac or Windows whatever IP address Docker Toolbox is using. So I went and entered:...
-
Thanks for the version number - I think us developers can make some improvements (from https://docs.docker.com/compose/environment-variables/ it seems like the .env file location changed on 1.28 which is why it wasn't found on yours. Maybe we could use inline defaults) Anyway back to your latest error. The "paster" executable should be available (inside the docker container) if all the previous commands ran correctly. My guess is that because of the sudo & environment problems earlier, the earlier...
-
docker-compose version 1.26.2, build eefe0d31 sudo -E sh -c 'docker-compose run taskd paster setup-app docker-dev.ini' Starting allura-git_mongo_1 ... done Creating allura-git_web_1 ... done Creating allura-git_outmail_1 ... done Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"paster\": executable file not found in $PATH": unknown
-
What version of docker-compose do you have? It'd be nice for us to figure out if older versions don't automatically use the .env file or if there's something else going on. In the commands you shared above, I think sudo is making the exported environment variable not pass through to the docker-compose command. Here's a few possible ways to make it work: https://askubuntu.com/questions/57915/environment-variables-when-run-with-sudo#57938 The second answer with sudo -E ... seems pretty convenient if...
-
kalmer@test:/projektid/allura-git/Allura$ export LOCAL_SHARED_DATA_ROOT=./allura-data kalmer@test:/projektid/allura-git/Allura$ sudo docker-compose run taskd paster setup-app docker-dev.ini [sudo] password for kalmer: WARNING: The LOCAL_SHARED_DATA_ROOT variable is not set. Defaulting to a blank string. Starting allura-git_solr_1 ... done Starting allura-git_mongo_1 ... done Creating allura-git_web_1 ... error ERROR: for allura-git_web_1 Cannot create container for service web: create .: volume name...
-
The volume names in the docker-compose.yml file are: - .:/allura # Allura source code from local host - ${LOCAL_SHARED_DATA_ROOT}:/allura-data # for virtualenv, scm repos, etc - ${LOCAL_SHARED_DATA_ROOT}/root/home:/root # for persistent home dir, mainly for pudb So my guess is that the LOCAL_SHARED_DATA_ROOT variable isn't getting set. The top of the CHANGES file explains a bit about it: [#8399] In an effort to update the Docker startup steps to make them as easy as possible and compatible across...
-
Installing on "Ubuntu 20.04" not possible
-
8405 added last_access field to save the last access date for OAuth tokens
-
OAuth Token Display Last Access Date
-
SMTP maximum allowed line length (part 2)
-
fixup! fix email headers being longer than SMTP limit
-
[#8404] fix email headers being longer than SMTP limit
-
good feedback. I updated and pushed to dw/8404
-
allura still supports python 3.6 so from __future__ import annotations won't work (added in 3.7). I believe the Apache jenkins build uses 3.6 and will error on that. that said, email.message is available in 3.6 so can be imported & used without any __future__ stuff can we keep MAX_MAIL_LINE_OCTETS at 990. that seems more conservative and safe since http://www.jebriggs.com/blog/2010/07/smtp-maximum-line-lengths/ indicates some email servers have a limit of 990 would be nice to have the commit message...
-
fix email headers being longer than SMTP limit
-
SMTP maximum allowed line length (part 2)
-
Hi, The unsubscribe commit looks pretty good. Would you able to add a test for it? For example test_new_admin_subscriptions covers when an admin user is added. It'd be nice to have a similar sort of test for when an admin user is removed. For the ticket & commit message linking, unfortunately I don't think it is quite the right direction. It does a lot of lookups & processing, so can be slow on large projects and sites. Also it is specifically for ticket pages and git commits, but it would be nice...
-
Fix non existing template import on Github importer template
-
LDAP pref improvements
-
Fix LdapUserPreferencesProvider.get_pref return. Support multi-valued ldap prefs
-
Change ldap to simple_bind_s (does same thing, lets mockldap be used in tests)
-
8403 added new project_url field with validator and tooltips
-
8403 added two new subtitles and improvements to the form, updated error message when project is not available in GH
-
8403 added field diver for SF project shortname and a on blur event on project_url to check for valid github url
-
Github Importer Enhancements
-
@guillermocruz, your changes to the github import flow on gc/8403 look great. Good job!
-
fixup! fixup! fixup! 8403 added field diver for SF project shortname and a on blur event on project_url to check for valid github url
-
fixup! fixup! 8403 added field diver for SF project shortname and a on blur event on project_url to check for valid github url
-
fixup! 8403 added field diver for SF project shortname and a on blur event on project_url to check for valid github url
-
8403 added field diver for SF project shortname and a on blur event on project_url to check for valid github url
-
8403 added two new subtitles and improvements to the form, updated error message when project is not available in GH
-
Adds method to fetch multiple troves by their IDs
-
fixup! 8403 added new project_url field with validator and tooltips
-
8403 added new project_url field with validator and tooltips
-
Github Importer Enhancements
-
Kenton Taylor committed [ec83d0]
Adds method to fetch multiple troves by their IDs
-
Add block to permit customization of user message notices
-
Add comment about additional nginx settings
-
LDAP pref improvements
-
Enhancements for backlinks from ticket to Git commit and unsubscribe feature
-
Preserve exact URL in pagination helper
-
Preserve exact URL in pagination helper
-
Remove PreChecked Checkboxes
-
[#8402] removed default precheck checkboxes on wiki, topic pages
-
Remove PreChecked Checkboxes
-
Looks good.
-
Upgrade Ming and dependencies
-
Looks good. Ticket closed.
-
Preserve exact URL in pagination helper
-
Test fix for logging tweak
-
[#8401] removed added test and updated test_project_icon in test_admin
-
Include the incoming mail task id in logging
-
Project Icon URL Param Issue
-
[#8400] Upgrade Ming 0.11.1 -> 0.11.2, and its deps: pymongo,pytz,six
-
8401 removed added test and updated test_project_icon in test_admin
-
Project Icon URL Param Issue
-
Fixed icon url issue when more than one 'w' url param is included and added a test
-
removed default checked attribute from checkboxes from wiki and topic forms unless they are replies and added a few tests
-
[#8400] Upgrade Ming 0.11.1 -> 0.11.2, and its deps: pymongo,pytz,six
-
Added checkbox option that sends message replies to users active email address
-
message replies to email address is persisted in user preferences, fixed wrong sender email address and reverted 'From' value changes
-
removed email address from FROM: field in form and fixed TestMailTasks
-
reverted FROM: field changes and set message_reply_real_address to false if checkbox is unchecked
-
Send Message Replies To User Email Address
-
Looks good to me!
-
reverted FROM: field changes and set message_reply_real_address to false if checkbox is unchecked
-
Upgrade Ming and dependencies
-
removed email address from FROM: field in form and fixed TestMailTasks
-
Have a field to track user registration date, not just rely on _id
-
Message replies to email address is saved in user preferences. Fixed wrong sender email address. Reverted 'From' value changes that were causing tests to fail.
-
Have a field to track user registration date, not just rely on _id
-
Send Message Replies To User Email Address
-
Add post/forum_post index
-
dataclasses is needed on py36 but cannot be installed by py37. OK to not declare it here, it'll get pulled in by werkzeug if needed
-
switch from npm install -> npm ci
-
Broken Docker Setup Guide and Config + werkzeug upgrade
-
Commit package-lock.json and convert to using `npm ci`