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.

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

.mackup.cfg [configuration_files] tag not being picked up #869

Open
rkpatel33 opened this issue Aug 24, 2016 · 9 comments
Open

.mackup.cfg [configuration_files] tag not being picked up #869

rkpatel33 opened this issue Aug 24, 2016 · 9 comments
Labels

Comments

@rkpatel33
Copy link

I have a .mackup.cfg file that looks like this:

image

But when I run mackup backup the .eslint file does not seem to get picked up. I have confirmed the target file and config files are where they should be:

image

Any thoughts?

Rishi

@acevif
Copy link

acevif commented Aug 30, 2016

I have same problem.

@yurikoles
Copy link

Me too

@lra lra added the TOFIX label Sep 1, 2016
@revolter
Copy link
Contributor

revolter commented Sep 7, 2016

Me too. @lra, can I help you with this?

@NewbMiao
Copy link

NewbMiao commented Sep 26, 2016

!!!THERE IS NO NEED TO DO THIS!!! see this

for now:
step 1:

cat .mackup/app-name.cfg
[application]
name = app-name

[configuration_files]
.some-config-file-name
.some-dir

THERE IS NO NEED TO DO THIS

step 2:

cat .mackup.cfg
[applications_to_sync]
app-name

then , mackup backup can work out!

@revolter
Copy link
Contributor

@lra, Shouldn't mackup backup the actual custom app config file created by the user that's used to sync configuration files? In @NewbMiao's example, the .mackup/app-name.cfg file.

@mbaechtold
Copy link
Contributor

mbaechtold commented Mar 3, 2017

One should omit step 2 or app-name will be the only app to be synced.

Syncing your custom files is explained in https://github.com/lra/mackup/tree/master/doc#add-support-for-an-application-or-any-file-or-directory.

@revolter
Copy link
Contributor

revolter commented Mar 3, 2017

So that's why Mackup wasn't working for me for the past almost half a year! Thanks a lot @mbaechtold.

@NewbMiao, please edit your answer so we won't have any more victims.

mbaechtold added a commit to mbaechtold/mackup that referenced this issue Mar 3, 2017
As reported in lra#869, the `[configuration_files]` section of the `.mackup.cfg` is not working as advertised in the `Configuration` chapter of the docs.

The users should be pointed to the section where the syncing of custom apps (and individual files) is explained until lra#869 has been fixed.
mbaechtold added a commit to mbaechtold/mackup that referenced this issue Mar 3, 2017
As reported in lra#869, the `[configuration_files]` section of the `.mackup.cfg` is not working as advertised in the `Configuration` chapter of the docs.

The users should be pointed to the section where the syncing of custom apps (and individual files) is explained until lra#869 has been fixed.
mbaechtold added a commit to mbaechtold/mackup that referenced this issue Mar 4, 2017
As reported in lra#869, the `[configuration_files]` section of the `.mackup.cfg` is not working as advertised in the `Configuration` chapter of the docs.

The users should be pointed to the section where the syncing of custom apps (and individual files) is explained until lra#869 has been fixed.
@pikeas
Copy link

pikeas commented May 2, 2017

Just bit by this!

@schemacs
Copy link

configuration_files only works for custom app cfg files. RotsiserMho#4 should also be ported to this repo.

mbaechtold added a commit to mbaechtold/mackup that referenced this issue Nov 17, 2020
As reported in lra#869, the `[configuration_files]` section of the `.mackup.cfg` is not working as advertised in the `Configuration` chapter of the docs.

The users should be pointed to the section where the syncing of custom apps (and individual files) is explained until lra#869 has been fixed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants