Charm needed: Gitlab

Bug #931835 reported by Jorge Castro
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Juju Charms Collection
Fix Released
Undecided
Helio Mota

Bug Description

http://gitlabhq.com/

This would be cool for a "starting my own company want my own infrastructure" use case.

Antono Vasiljev (antono)
Changed in charms:
assignee: nobody → Antono Vasiljev (antono)
Revision history for this message
David Overcash (funnylookinhat) wrote :

Not sure if this helps or not - but I found the shell scripts and instructions here to be fairly straightforward - and I tested them through 12.04.

https://github.com/gitlabhq/gitlabhq_install/blob/master/README.md

I'm sure that pulling those together into a charm along with a ruby dependency would do the trick! Let me know if I can help in any way.

Revision history for this message
David Overcash (funnylookinhat) wrote :

Antono - Are you working on this? If not I'll consider trying to whip it up over the weekend.

Marco Ceppi (marcoceppi)
Changed in charms:
assignee: Antono Vasiljev (antono) → Marco Ceppi (marcoceppi)
Colan Schwartz (colan)
Changed in charms:
status: New → Confirmed
Revision history for this message
Jorge Castro (jorge) wrote :

https://github.com/gitlabhq/gitlabhq/blob/stable/doc/installation.md

New version, also check out their installation script, this page is basically a HOWTO for the charm!

Revision history for this message
Helio Mota (helio-mota) wrote :

Initial charm pushed to lp:~helio-mota/charms/precise/gitlab/trunk

Note that I had to include a step that precompiles the entire gitlab rails app even before nginx is started. If that is not done nginx returns HTTP 502 errors while waiting for rails to compile the app. The pre-compile step is somewhat long (15 minutes) on a t1.micro machine.

The hooks are based of the official install guide shared by Jorge before.

Changed in charms:
assignee: Marco Ceppi (marcoceppi) → hlm (helio-mota)
Revision history for this message
Brandon Holtsclaw (imbrandon) wrote :

After a quick review it looks like you have an empty relation, this is not a good idea, you should at least set IP and PORT in this or remove it.

Also it looks like there are some left over items from another charm you may have used as a template inside of inc/common :
config_file_path="$install_path/configuration.php"
initdb_sql="$install_path/installation/sql/mysql/joomla.sql"

Changed in charms:
status: Confirmed → Incomplete
Revision history for this message
Helio Mota (helio-mota) wrote :

Hi Brandon,

Thanks for the feedback. I have made the updates and commited the fix.

-Helio

Changed in charms:
status: Incomplete → Fix Committed
Revision history for this message
Juan L. Negron (negronjl) wrote :
Revision history for this message
Juan L. Negron (negronjl) wrote :

Hello:

Would you review the README.md file to reflect a bit more information as to the username and password needed to log on to the GitLab Web UI?

It's not obvious to me what the username should be as the form is asking for an email address yet the config.yaml file only provides an option for admin_password.

I would be happy to review the charm again once the changes above are addressed.

Thanks,

Juan

Changed in charms:
status: Fix Committed → Incomplete
Revision history for this message
Helio Mota (helio-mota) wrote :

Juan,

Thank you for the feedback. I improved the README.md wording to include a "how to access gitlab" installed by the charm for the first time.

For now I've left the default admin user name that is created by gitlab's db migrations. I plan to have the admin name as a config option in near future.

-Helio

Helio Mota (helio-mota)
Changed in charms:
status: Incomplete → Fix Committed
Revision history for this message
Juan L. Negron (negronjl) wrote :

Reviewing this now.

-Juan

Revision history for this message
Juan L. Negron (negronjl) wrote :

Approved.

Promulgated.

Nice job.

-Juan

Changed in charms:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.