You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <da...@brondsema.net> on 2015/06/29 17:57:23 UTC
[allura:tickets] #5943 Post-setup instructions
---
** [tickets:#5943] Post-setup instructions**
**Status:** open
**Milestone:** unreleased
**Labels:** docs bitesize getting-started sf-current sf-4
**Created:** Fri Mar 08, 2013 05:03 PM UTC by Dave Brondsema
**Last Updated:** Mon Feb 16, 2015 04:15 PM UTC
**Owner:** nobody
After README, there are a lot of things to do to really get started, which aren't explained:
* what neighborhoods are
* how to get to a nbhd admin page and configure stuff
* remove default users: `db.user.update({username:/test/}, {$set: {disabled:true}}, false, true);db.user.update({username:/root/}, {$set: {disabled:true}}, false, true);db.user.update({username:/admin/}, {$set: {disabled:true}}, false, true);`
* remove adobe nbhd: `db.neighborhood.remove({url_prefix:'/adobe/'})`
* remove test project: `db.project.remove({shortname:'test'}) // may need to add a neighborhood_id`
parameter if the project name exists in more than one nbhd.
* change `[handler_console]` in the ini file to use `allura.lib.utils.CustomWatchedFileHandler` so that it goes to a file and gets task info included
* change `beaker.session.secret` and `beaker.session.validate_key` in the `.ini` file to new values (first used for simple cookies, latter used for encrypted cookies)
Several of these are explained in default wiki content now.
docs/installation.rst has some post-setup content which should be freshened, and enhanced to include more.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Ticket 5943 discussion
Posted by Dave Brondsema <da...@brondsema.net>.
- **labels**: docs, bitesize, getting-started, sf-current, sf-4 --> docs, bitesize, getting-started, sf-4
---
** [tickets:#5943] Post-setup instructions**
**Status:** review
**Milestone:** unreleased
**Labels:** docs bitesize getting-started sf-4
**Created:** Fri Mar 08, 2013 05:03 PM UTC by Dave Brondsema
**Last Updated:** Fri Jul 10, 2015 09:54 AM UTC
**Owner:** Igor Bondarenko
After README, there are a lot of things to do to really get started, which aren't explained:
* what neighborhoods are
* how to get to a nbhd admin page and configure stuff
* remove default users: `db.user.update({username:/test/}, {$set: {disabled:true}}, false, true);db.user.update({username:/root/}, {$set: {disabled:true}}, false, true);db.user.update({username:/admin/}, {$set: {disabled:true}}, false, true);`
* remove adobe nbhd: `db.neighborhood.remove({url_prefix:'/adobe/'})`
* remove test project: `db.project.remove({shortname:'test'}) // may need to add a neighborhood_id`
parameter if the project name exists in more than one nbhd.
* change `[handler_console]` in the ini file to use `allura.lib.utils.CustomWatchedFileHandler` so that it goes to a file and gets task info included
* change `beaker.session.secret` and `beaker.session.validate_key` in the `.ini` file to new values (first used for simple cookies, latter used for encrypted cookies)
Several of these are explained in default wiki content now.
docs/installation.rst has some post-setup content which should be freshened, and enhanced to include more.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Ticket 5943 discussion
Posted by Dave Brondsema <da...@brondsema.net>.
- **labels**: docs, bitesize, getting-started, sf-1 --> docs, bitesize, getting-started, sf-current, sf-4
- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -6,7 +6,6 @@
* remove adobe nbhd: `db.neighborhood.remove({url_prefix:'/adobe/'})`
* remove test project: `db.project.remove({shortname:'test'}) // may need to add a neighborhood_id`
parameter if the project name exists in more than one nbhd.
-* how to deploy svn, hg, or git backend services and integrate them with Allura auth [#5424]
* change `[handler_console]` in the ini file to use `allura.lib.utils.CustomWatchedFileHandler` so that it goes to a file and gets task info included
* change `beaker.session.secret` and `beaker.session.validate_key` in the `.ini` file to new values (first used for simple cookies, latter used for encrypted cookies)
~~~~
---
** [tickets:#5943] Post-setup instructions**
**Status:** open
**Milestone:** unreleased
**Labels:** docs bitesize getting-started sf-current sf-4
**Created:** Fri Mar 08, 2013 05:03 PM UTC by Dave Brondsema
**Last Updated:** Mon Feb 16, 2015 04:15 PM UTC
**Owner:** nobody
After README, there are a lot of things to do to really get started, which aren't explained:
* what neighborhoods are
* how to get to a nbhd admin page and configure stuff
* remove default users: `db.user.update({username:/test/}, {$set: {disabled:true}}, false, true);db.user.update({username:/root/}, {$set: {disabled:true}}, false, true);db.user.update({username:/admin/}, {$set: {disabled:true}}, false, true);`
* remove adobe nbhd: `db.neighborhood.remove({url_prefix:'/adobe/'})`
* remove test project: `db.project.remove({shortname:'test'}) // may need to add a neighborhood_id`
parameter if the project name exists in more than one nbhd.
* change `[handler_console]` in the ini file to use `allura.lib.utils.CustomWatchedFileHandler` so that it goes to a file and gets task info included
* change `beaker.session.secret` and `beaker.session.validate_key` in the `.ini` file to new values (first used for simple cookies, latter used for encrypted cookies)
Several of these are explained in default wiki content now.
docs/installation.rst has some post-setup content which should be freshened, and enhanced to include more.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Ticket 5943 discussion
Posted by Dave Brondsema <da...@brondsema.net>.
- **status**: review --> closed
- **Reviewer**: Dave Brondsema
---
** [tickets:#5943] Post-setup instructions**
**Status:** closed
**Milestone:** unreleased
**Labels:** docs bitesize getting-started sf-4
**Created:** Fri Mar 08, 2013 05:03 PM UTC by Dave Brondsema
**Last Updated:** Mon Jul 13, 2015 02:50 PM UTC
**Owner:** Igor Bondarenko
After README, there are a lot of things to do to really get started, which aren't explained:
* what neighborhoods are
* how to get to a nbhd admin page and configure stuff
* remove default users: `db.user.update({username:/test/}, {$set: {disabled:true}}, false, true);db.user.update({username:/root/}, {$set: {disabled:true}}, false, true);db.user.update({username:/admin/}, {$set: {disabled:true}}, false, true);`
* remove adobe nbhd: `db.neighborhood.remove({url_prefix:'/adobe/'})`
* remove test project: `db.project.remove({shortname:'test'}) // may need to add a neighborhood_id`
parameter if the project name exists in more than one nbhd.
* change `[handler_console]` in the ini file to use `allura.lib.utils.CustomWatchedFileHandler` so that it goes to a file and gets task info included
* change `beaker.session.secret` and `beaker.session.validate_key` in the `.ini` file to new values (first used for simple cookies, latter used for encrypted cookies)
Several of these are explained in default wiki content now.
docs/installation.rst has some post-setup content which should be freshened, and enhanced to include more.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Ticket 5943 discussion
Posted by Igor Bondarenko <je...@gmail.com>.
- **status**: open --> in-progress
- **assigned_to**: Igor Bondarenko
---
** [tickets:#5943] Post-setup instructions**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** docs bitesize getting-started sf-current sf-4
**Created:** Fri Mar 08, 2013 05:03 PM UTC by Dave Brondsema
**Last Updated:** Mon Jun 29, 2015 03:57 PM UTC
**Owner:** Igor Bondarenko
After README, there are a lot of things to do to really get started, which aren't explained:
* what neighborhoods are
* how to get to a nbhd admin page and configure stuff
* remove default users: `db.user.update({username:/test/}, {$set: {disabled:true}}, false, true);db.user.update({username:/root/}, {$set: {disabled:true}}, false, true);db.user.update({username:/admin/}, {$set: {disabled:true}}, false, true);`
* remove adobe nbhd: `db.neighborhood.remove({url_prefix:'/adobe/'})`
* remove test project: `db.project.remove({shortname:'test'}) // may need to add a neighborhood_id`
parameter if the project name exists in more than one nbhd.
* change `[handler_console]` in the ini file to use `allura.lib.utils.CustomWatchedFileHandler` so that it goes to a file and gets task info included
* change `beaker.session.secret` and `beaker.session.validate_key` in the `.ini` file to new values (first used for simple cookies, latter used for encrypted cookies)
Several of these are explained in default wiki content now.
docs/installation.rst has some post-setup content which should be freshened, and enhanced to include more.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Re: Ticket 5943 discussion
Posted by Igor Bondarenko <je...@gmail.com>.
I didn't start it yet. I'm planning to work on it today. That sounds like a good idea, I'll give it a try!
---
** [tickets:#5943] Post-setup instructions**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** docs bitesize getting-started sf-current sf-4
**Created:** Fri Mar 08, 2013 05:03 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 08, 2015 06:46 PM UTC
**Owner:** Igor Bondarenko
After README, there are a lot of things to do to really get started, which aren't explained:
* what neighborhoods are
* how to get to a nbhd admin page and configure stuff
* remove default users: `db.user.update({username:/test/}, {$set: {disabled:true}}, false, true);db.user.update({username:/root/}, {$set: {disabled:true}}, false, true);db.user.update({username:/admin/}, {$set: {disabled:true}}, false, true);`
* remove adobe nbhd: `db.neighborhood.remove({url_prefix:'/adobe/'})`
* remove test project: `db.project.remove({shortname:'test'}) // may need to add a neighborhood_id`
parameter if the project name exists in more than one nbhd.
* change `[handler_console]` in the ini file to use `allura.lib.utils.CustomWatchedFileHandler` so that it goes to a file and gets task info included
* change `beaker.session.secret` and `beaker.session.validate_key` in the `.ini` file to new values (first used for simple cookies, latter used for encrypted cookies)
Several of these are explained in default wiki content now.
docs/installation.rst has some post-setup content which should be freshened, and enhanced to include more.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Ticket 5943 discussion
Posted by Dave Brondsema <da...@brondsema.net>.
Hey Igor,
Not sure how far you've gotten with this, but Heith and I were talking about it a few days ago and had an idea. Instead of telling people how to delete the test content, maybe we want 2 different ways to run `setup-app` (bootstrap.py). One with sample content and one without.
---
** [tickets:#5943] Post-setup instructions**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** docs bitesize getting-started sf-current sf-4
**Created:** Fri Mar 08, 2013 05:03 PM UTC by Dave Brondsema
**Last Updated:** Tue Jul 07, 2015 11:58 AM UTC
**Owner:** Igor Bondarenko
After README, there are a lot of things to do to really get started, which aren't explained:
* what neighborhoods are
* how to get to a nbhd admin page and configure stuff
* remove default users: `db.user.update({username:/test/}, {$set: {disabled:true}}, false, true);db.user.update({username:/root/}, {$set: {disabled:true}}, false, true);db.user.update({username:/admin/}, {$set: {disabled:true}}, false, true);`
* remove adobe nbhd: `db.neighborhood.remove({url_prefix:'/adobe/'})`
* remove test project: `db.project.remove({shortname:'test'}) // may need to add a neighborhood_id`
parameter if the project name exists in more than one nbhd.
* change `[handler_console]` in the ini file to use `allura.lib.utils.CustomWatchedFileHandler` so that it goes to a file and gets task info included
* change `beaker.session.secret` and `beaker.session.validate_key` in the `.ini` file to new values (first used for simple cookies, latter used for encrypted cookies)
Several of these are explained in default wiki content now.
docs/installation.rst has some post-setup content which should be freshened, and enhanced to include more.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] Ticket 5943 discussion
Posted by Igor Bondarenko <je...@gmail.com>.
- **status**: in-progress --> review
- **Comment**:
Closed #815. `ib/5943`
QA:
- checkout branch
- run `ALLURA_TEST_DATA=False paster setup-app development.ini` (change db settings first, if you don't want to rewrite existing data)
- make sure there's no test users, projects, adobe neighborhood, etc
- `cd Allura/docs && make html`
- review "Installation -> Post-setup instructions" and "Using Allura -> What are neighborhoods?" sections
English is not my native language, so there's definitely some silly mistakes. Feel free to fix them :)
---
** [tickets:#5943] Post-setup instructions**
**Status:** review
**Milestone:** unreleased
**Labels:** docs bitesize getting-started sf-current sf-4
**Created:** Fri Mar 08, 2013 05:03 PM UTC by Dave Brondsema
**Last Updated:** Wed Jul 08, 2015 06:46 PM UTC
**Owner:** Igor Bondarenko
After README, there are a lot of things to do to really get started, which aren't explained:
* what neighborhoods are
* how to get to a nbhd admin page and configure stuff
* remove default users: `db.user.update({username:/test/}, {$set: {disabled:true}}, false, true);db.user.update({username:/root/}, {$set: {disabled:true}}, false, true);db.user.update({username:/admin/}, {$set: {disabled:true}}, false, true);`
* remove adobe nbhd: `db.neighborhood.remove({url_prefix:'/adobe/'})`
* remove test project: `db.project.remove({shortname:'test'}) // may need to add a neighborhood_id`
parameter if the project name exists in more than one nbhd.
* change `[handler_console]` in the ini file to use `allura.lib.utils.CustomWatchedFileHandler` so that it goes to a file and gets task info included
* change `beaker.session.secret` and `beaker.session.validate_key` in the `.ini` file to new values (first used for simple cookies, latter used for encrypted cookies)
Several of these are explained in default wiki content now.
docs/installation.rst has some post-setup content which should be freshened, and enhanced to include more.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.