Re: how to post image on project front page

[Amanda Sunyoto]

That's perfect.

Thank you!

-Amanda

On Wed, Oct 12, 2016 at 6:11 AM, Aleksey Tsalolikhin <
alek...@verticalsysadmin.com> wrote:

> Dear Amanda,
>
> I tried embedding HTML and Markdown-formatted images into Project
> Description but they didn't get rendered.
>
> Would embedding an image in the project README.md work for you?
>
> The README is displayed automatically when you go to the project page.
>  e.g., http://your/image.gif>
>
> Just put that at the top of your README.
>
> You could also upload a 200K image as your project avatar (under Edit
> Project) but I would not recommend it for a project timeline, the graphic
> would be too small.  The README is the way to go.
>
> Best,
> Aleksey Tsalolikhin
> Vertical Sysadmin, Inc.
> Authorized GitLab training partner
>
> On Oct 6, 2016 1:30 PM,  wrote:
>
>> Hello,
>>
>> Is there a way to post an image in the front page of the project? We
>> would like to post a picture of the project timeline without it being a
>> link,
>>
>> Thank you,
>> Amanda Sunyoto
>>
>> --
>> 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 gitlabhq+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/gitlabhq/6d8b6065-4028-4e9c-a970-023cb7ff7a65%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> ᐧ
> ᐧ
>



-- 
Amanda Allison Sunyoto
University of California, Los Angeles
B.A. Chinese 2015
A.A. Dental Assisting, A.A. Natural Science 2012
Volunteers Around the World-UCLA Chapter | President/Co-founder
Chinese Taipei Skating Union | National Team Member

Email:   amanda.suny...@gmail.com
Phone: (626) 354-8422

-- 
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 gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/CAGEZYiTaZfUwP01_7gOoVZJWQzeFgZYeoHEWGf0PFGjqKCj-1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to post image on project front page

[Aleksey Tsalolikhin]

Dear Amanda,

I tried embedding HTML and Markdown-formatted images into Project
Description but they didn't get rendered.

Would embedding an image in the project README.md work for you?

The README is displayed automatically when you go to the project page.
 e.g., http://your/image.gif>

Just put that at the top of your README.

You could also upload a 200K image as your project avatar (under Edit
Project) but I would not recommend it for a project timeline, the graphic
would be too small.  The README is the way to go.

Best,
Aleksey Tsalolikhin
Vertical Sysadmin, Inc.
Authorized GitLab training partner

On Oct 6, 2016 1:30 PM,  wrote:

> Hello,
>
> Is there a way to post an image in the front page of the project? We would
> like to post a picture of the project timeline without it being a link,
>
> Thank you,
> Amanda Sunyoto
>
> --
> 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 gitlabhq+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/gitlabhq/6d8b6065-4028-4e9c-a970-023cb7ff7a65%40googlegroups.com
> 
> .
> 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 gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/CANNWuVWY6Qd-SFpem7dvogW2W_KqM1fN64xjKtX_0%3DeNriqbng%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: 500 Error after update to 8.12.3 (MissingAttributeError)

[Urs Liska]

There have been some updates to the gitlab-ce package in the meantime,
but they don't sort out my problem that my Gitlab instance isn't
available. I'm desperately in need to get this running again and so
would be glad about any advice or even guesses.

Urs



gitlab-rake db:migrate
gitlab-rake db:migrate:status
gitlab-rake gitlab:check

all return "OK" (and have always been throughout this process).

But the end of my production.log is now different than in the beginning
and is actually telling me to check config files (which it hadn't
originally):

Started GET "/" for 188.98.168.133 at 2016-10-12 10:37:13 +0200
Processing by RootController#index as HTML
Completed 401 Unauthorized in 43ms (ActiveRecord: 6.9ms)
Started GET "/users/sign_in" for 188.98.168.133 at 2016-10-12 10:37:14 +0200
Processing by SessionsController#new as HTML
Completed 500 Internal Server Error in 46ms (ActiveRecord: 6.0ms)

LoadError (cannot load such file -- devise/parameter_sanitizer):
  app/controllers/application_controller.rb:233:in
`configure_permitted_parameters'
  lib/gitlab/middleware/go.rb:16:in `call'


Invalid cron_jobs config key: 'historical_data_worker'. Check your
gitlab config file.
Invalid cron_jobs config key: 'update_all_mirrors_worker'. Check your
gitlab config file.
Invalid cron_jobs config key: 'update_all_remote_mirrors_worker'. Check
your gitlab config file.
Invalid cron_jobs config key: 'ldap_sync_worker'. Check your gitlab
config file.
Invalid cron_jobs config key: 'geo_bulk_notify_worker'. Check your
gitlab config file.
** [Raven] Raven 2.0.2 configured not to capture errors.
** [Raven] Raven 2.0.2 configured not to capture errors.



Am 02.10.2016 um 17:31 schrieb Urs Liska:
>
> One more item to debug: accessing repositories over ssh (git@... URLs)
> works fine, but direct Git access through https: URLs does *not*. So
> the Gitlab application does work obviously, only not HTTPS and thus
> the web interface
>
>
> Am 02.10.2016 um 16:29 schrieb Urs Liska:
>>
>> Hmm, after doing an apt-get dist-upgrade (Gitlab was updated during
>> "apt-get upgrade") I get the following error log:
>>
>> # tail -n 25 /var/log/gitlab/gitlab-rails/production.log
>>
>> Started GET "/" for 79.194.101.200 at 2016-10-02 16:28:06 +0200
>> Processing by RootController#index as HTML
>> Completed 500 Internal Server Error in 60ms (ActiveRecord: 9.0ms)
>>
>> LoadError (cannot load such file --
>> active_record/associations/has_many_through_association):
>>   app/models/user.rb:830:in `projects_union'
>>   app/models/user.rb:418:in `authorized_projects'
>>   app/controllers/dashboard/projects_controller.rb:7:in `index'
>>   app/controllers/root_controller.rb:13:in `index'
>>   lib/gitlab/middleware/go.rb:16:in `call'
>>
>>
>> Started GET "/" for 79.194.101.200 at 2016-10-02 16:28:08 +0200
>> Processing by RootController#index as HTML
>> Completed 500 Internal Server Error in 52ms (ActiveRecord: 2.8ms)
>>
>> LoadError (cannot load such file --
>> active_record/associations/has_many_through_association):
>>   app/models/user.rb:830:in `projects_union'
>>   app/models/user.rb:418:in `authorized_projects'
>>   app/controllers/dashboard/projects_controller.rb:7:in `index'
>>   app/controllers/root_controller.rb:13:in `index'
>>   lib/gitlab/middleware/go.rb:16:in `call'
>>
>>
>>
>> Am 02.10.2016 um 15:59 schrieb Urs Liska:
>>>
>>> I noticed one more thing:
>>>
>>> I'm running Gitlab on nginx, and my gitlab.rb contains an entry
>>>
>>> nginx['enable'] = false
>>>
>>> while gitlab.rb.save has this set to true.
>>>
>>> Can this be the source of the issue?
>>>
>>>
>>> Am 02.10.2016 um 15:48 schrieb Urs Liska:

 I had not done db:migrate before but db:migrate:status had
 exclusively reported "up" entries. Doing db:migrate now didn't
 change anything unfortunately.

 also gitlab-rake gitlab:check

 succeeded.

 Any further ideas?

 Urs


 Am 02.10.2016 um 15:42 schrieb Stan Hu:
> This sounds like a missing migration. Have you tried running the
> following?
>
> sudo gitlab-rake db:migrate:status
> sudo gitlab-rake db:migrate
>
> On Sun, Oct 2, 2016 at 6:39 AM, Urs Liska  > wrote:
>
> It seems it's a common problem that after updating Gitlab-omnibus
> something doesn't work anymore.
>
> This time, updating from (ca.) 8.10 to 8.12.3 causes "500"
> errors to
> appear on any page request, so I can't use Gitlab at all.
>
> gitlab-rake gitlab:env:info
>
> System information
> System:Ubuntu 14.04
> Current User:git
> Using RVM:no
> Ruby Version:2.3.1p112
> Gem Version:2.6.6
> Bundler Version:1.13.1
> Rake Version:10.5.0
> Sidekiq Version:4.1.4
>
> GitLab information
>