Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #6669

Closed
Open
Created Apr 01, 2014 by Administrator@rootOwner

load different assets when run gitlab in different port

Created by: poc7667

Because my gitlab's layout is totally broken,

So I decided run by manually in stead of ``

At first , my gitlab works fine, but crashed when I do rake assets:clean assets:precompile cache:clear RAILS_ENV=production, service gitlab restart

I used the Nginx to forward port 1987 to my gitlab app folder.

So I could access my gitlab site by http://localhost:1987

Now, I disabled the Nginx to forward the port 1987 to my gitlab app.

but rails s -p 1987 -e production stills shows the broken layout

if I run the server on other ports it works correctly excepts can not load avatar image

rails s -p 1999 -e production

enter image description here

enter image description here

Assignee
Assign to
Time tracking