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

List server requirements (=needed commands, e.g. rsync, readlink) in docs #803

Open
rintisch opened this issue Jan 31, 2025 · 2 comments
Open

Comments

@rintisch
Copy link

While looking for a deployment tool for a TYPO3 website on a shared hosting i came first across deployer and now had a look at Surf. Unfortunately are both not an option in my case as the hoster does not make readlink avaliable due to security reason.

I think it would be nice to see directly which commands are used by the tool (I made a similar post for deployer: deployphp/deployer#4012)

@simonschaufi
Copy link
Collaborator

It looks like you have a really bad hoster. Readlink is an essential part of a good deployment tool to know the real path of a symlink in order to allow rollback again. If you can't convince the hoster to provide this tool, the only option I see to deploy is to use rsync directly and if that is also not available, you have to use sftp but that is the worst solution. I would better switch the hoster in this situation

@rintisch
Copy link
Author

rintisch commented Feb 1, 2025

Thanks for the long response. I have access to multiple other hosters and realized already that all other allow those commands. So yes, I will use another hoster for this project.
With all other stuff I am really satisfied (support, quality, transparency, communication, ...).

The "project" is just a test and it is a shared hosting which is "driven" with Plesk. For other projects I am using a VPS.

The support answered by the way:

readlink is a system tool which poses some risks in a chrooted environment. Among other things because file references in a chrooted environment do not necessarily correspond to those that are actually on the file system.

I am not an expert at all but I will accept it and choose another hoster for the project.

Thanks for your answer. I think we can close this ticket in this case as it does not seem to be a problem for other people. But that's you who decide :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants