Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add examples for manipulating the sources #91

Closed
arnaudmm opened this issue Jun 8, 2017 · 2 comments
Closed

Add examples for manipulating the sources #91

arnaudmm opened this issue Jun 8, 2017 · 2 comments
Labels
docs examples Compose/Dockerfile/etc

Comments

@arnaudmm
Copy link

arnaudmm commented Jun 8, 2017

Hi,

Upgrade process (rsync) is way much better that the legacy one (tar) but I'm facing an issue when upgrading as I edited some files like .user.ini : they got reseted

Any advice/tips on how to avoid that ?
@SnowMB
Copy link
Contributor

SnowMB commented Jun 19, 2017

Hey,

I got an idea for your problem. You write our own derived Dockerfile and copy the modified files to the folder '/usr/src/nextcloud'. So when the upgrade process kick in, the new sources contain your files.

It would look something like this:

FROM nextcloud

COPY <your_user.ini> /usr/src/nextcloud/.user.ini

This was referenced Jun 19, 2017
Closed
Closed
@arnaudmm
Copy link
Author

It looks fair enough, I will try! Thanks

@tilosp tilosp mentioned this issue Jul 6, 2017
Merged
15 tasks
@tilosp tilosp changed the title Upgrade process and exclude files/dir Add examples for manipulating the sources Sep 24, 2017
@tilosp tilosp added the examples Compose/Dockerfile/etc label Jan 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
docs examples Compose/Dockerfile/etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@joshtrichards @arnaudmm @SnowMB @tilosp