Skip to content
  • Unwatch
    Notifications
  • Fork

    Fork Ocelot-Social

    If this dialog fails to load, you can visit the fork page directly.

Open with

feat: [WIP] 🍰 Rebranding And White-Labeling #3934

Open
wants to merge 39 commits into
base: master
from
Open

Conversation

@Mogge

Pick your reaction

Copy link Report content
Member

@Mogge Mogge commented 6 days ago

cake Pullrequest

Have all the information for the brand in separate config files. Set these defaults to ocelot.social

Select a reply ctrl .

The content you are editing has changed. Please copy your edits and refresh the page.

Nothing to preview

roschaefer added 30 commits on Jun 4
..plus get rid of obsolete prefix `nitro-`.
…_on_production

feat: Avoid new builds on base docker-compose.yml
Version was out of date anyways
* removed obsolete images
* moved all overwritable images to a location webapp/static/img/custom/
* better names
This link is helpful but points to Human Connection, so unfortunately I
have to remove it.
The links specified in the locales were pointing to the English site and
were mostly broken anyways.
I removed it. We cannot parameterize localizations with absolute urls
properly.
* imprint
* data privacy
* terms of service
* code of conduct
@Tirokk Tirokk changed the title feat: Rebranding and White-Labeling feat: [WIP] 🍰 Rebranding And White-Labeling 4 days ago
Mogge added 2 commits 3 hours ago

Merge state

Add more commits by pushing to the white-labeling branch on Ocelot-Social-Community/Ocelot-Social.

Review required

At least 1 approving review is required by reviewers with write access. Learn more.

All checks have passed

2 successful checks
@github-actions
CI / Continuous Integration (push) Successful in 8m
@travis-ci
Travis CI - Branch Successful in 20m — Build Passed
Resolve conflicts

This branch has conflicts that must be resolved

Use the web editor or the to resolve conflicts.

Conflicting files

neo4j/Dockerfile

or view .

Checkout via command line

If you cannot merge a pull request automatically here, you have the option of checking it out via command line to resolve conflicts and perform a manual merge.

Step 1: From your project repository, bring in the changes and test.

git fetch origin
git checkout -b white-labeling origin/white-labeling
git merge master

Step 2: Merge the changes and update on GitHub.

git checkout master
git merge --no-ff white-labeling
git push origin master
@Mogge

Couldn’t update branch

Oops, something went wrong.

@Mogge
Select a reply ctrl .
Remember, contributions to this repository should follow its contributing guidelines and code of conduct.
ProTip! Add comments to specific lines under Files changed.
Projects
Projects
None yet
Linked issues
Link an issue from this repository

Successfully merging this pull request may close these issues.

None yet

2 participants
Lock conversation

Lock conversation on this pull request

  • Other users can’t add new comments to this pull request.
  • You and other members of teams with write access to this repository can still leave comments that others can see.
  • You can always unlock this pull request again in the future.

Optionally, choose a reason for locking that others can see. Learn more about when it’s appropriate to lock conversations.

You can’t perform that action at this time.