Forums Archived

This forum has been archived. No new posts can be made and no new users can sign up. It remains here for reference only.

Find the new forums here

File locations

  • Last Post 12 September 2021
Rulenine posted this 31 May 2021

Hi all,

I'm using AMP to manage a minecraft server. I have the panel access with file manager, but can't seen to figure out where on my CentOS server AMP is putting all the files. I'm uncomfortable only being able to manage it from the amp panel - I need access to all the files directly so that, if required, I can manually backup, make copies, edit settings, etc. Anyone able to help?


  • Liked by
  • Leeham
Order By: Standard | Newest | Votes
Mike posted this 01 June 2021

You shouldn't touch them directly, you can damage your installation by doing this. Connect using an SFTP client using the 'connect to sftp' button in the top right of the file manager.

Rulenine posted this 01 June 2021

I get that, and I have no plans to be messing regularly with then. Nevertheless, unlike all servers I previously had running either unmanaged or with McMyAdmin, I cannot find where these files are located. I'd like to know where AMP is putting them at the very least. I can also do things such as once a week manually back up to an external drive without having to rely on AMP. I don't like not knowing where a piece of software is putting files and data.

  • Liked by
  • Leeham
Mike posted this 01 June 2021

Look for hidden files :)

It's actually hidden deliberately on Linux as a basic competency test. If you can find it, you can touch it.

bbqchipsy posted this 12 September 2021

Is there any need to be so vague and condescending?

It's quite a simple question and very reasonable to want to know where your PAID software is putting it's files.

  • Liked by
  • Leeham
  • docbray
Mike posted this 12 September 2021

We're British, vagueness is what we do. But it's not about being condescending.

It's all in the amp users home directory.

The reason we don't necessarily give the direct answer is to avoid situations where what we're doing is essentially teaching people how to use Linux (because the support cost of doing this is immense). One of the most common mistakes users make is touching AMPs files as the wrong user and damaging their installation. It's why the location is hidden with a dot prefix so that only users who know to do ls -a in /home/amp find it.

Experienced Linux users usually find the files pretty fast because they're in a fairly straightforward location or they know how to search the system.

So we might give a vague answer in some cases to encourage users to learn to use the OS better, otherwise we end up with users who are touching files directly because we just gave them the answer but aren't familiar enough with the OS to not make common mistakes that we can't mitigate. It's why AMP has built-in SFTP to access files which puts AMP in control of some of this to avoid common pitfalls and why we advocate users doing it that way rather than touching the filesystem directly. It's not about trying to be obscure or condescending, but about the long-term results. There's a lot of users and not a lot of us.