To add to what I am referring to in my earlier statement. Looking at 
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/README.md

You have a section for running in development mode and to run the tests etc. It 
only shows the bundle exec command. It doesn't show from what directory that 
command needs to be run from and/or as what user (if your RPM created another 
user). This is where my confusion is. If I wanted to run bundle exec rails 
console or even those commands that you have in that readme, I am not able to 
use that readme as a reference because it doesn't tell me what directory I need 
to be in in order for that command to run successfully.

On Mar 24, 2014, at 8:10 AM, Vell <[email protected]> wrote:

> I read that entire read me before asking my question. That doesn't seem to 
> tell me what I need to know. I could have asked my questions incorrect and if 
> so I apologize.
> 
> What exactly I am looking for:
> How to get into the rails console to look at the data. The directory 
> structure in /opt/gitlab doesn't look anything like a rails app. So I am 
> trying to find what directory I need to be in and as what user in order to 
> get into there rails console and look at the data?
> 
> If it is /opt/gitlab then simply doing a `bundle exec rails console ` in that 
> directly does not work, at least as root which is the account I used to 
> install this.
> 
> 
> My thought process is:
> 
> cd into directory
> bundle exec rails console
> Model.all # to view my data
> 
> I don't see anywhere in your documentation where it explicitly tells me that  
> (or something like that). I also don't see anything regarding general 
> administration (aside from creating and restoring backups) of this system 
> once it is up and running.
> 
> Any suggestions on where to look for this information or how I can do what I 
> need to do to get started?
> 
> On Mar 24, 2014, at 4:34 AM, Sytse Sijbrandij <[email protected]> wrote:
> 
>> Please see https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
>> 
>> It is in: /opt/gitlab holds application code for GitLab and its dependencies.
>> 
>> On Fri, Mar 21, 2014 at 4:50 PM, Vell <[email protected]> wrote:
>>> Background:
>>> OS: Centos 6.5
>>> GitLab: gitlab-6.6.5_omnibus-1.el6.x86_64.rpm (installed as root user)
>>> Issue: How to launch rails console to view data
>>> 
>>> Hello all,
>>> 
>>> I am attempting to figure out how to launch rails console for the gitlab
>>> application so I can take a look a the data as needed. What is prompting
>>> this is that I have just created a user but I have not seen the confirmation
>>> email.
>>> 
>>> While I know taking a look at the data won't necessarily fix my current
>>> issue, I still would like to know where the application is housed so that
>>> whenever I need to look at it I can.
>>> 
>>> Based on what I read in the documentation it should be stored in
>>> /home/git/gitlab but when I change to my git user there isn't a gitlab
>>> directory.
>>> 
>>> Can anyone tell me where I can find the documentation related to
>>> administering gitlab or at the very least the documentation on how to view
>>> the data?
>>> 
>>> Thanks in advance.
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "GitLab" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "GitLab" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/gitlabhq/q7uEo7rJ64w/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected].
>> For more options, visit https://groups.google.com/d/optout.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to