-
Notifications
You must be signed in to change notification settings - Fork 411
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
Maintain the repository #265
Comments
Hi Julien, Could you please merge this fix before abandoning Sharrre? It will prevent Sharrre from killing my servers... Thank you, |
Done Maarten |
Thank you so much! I've had to manually contact several big sites that were using a modified Sharrre because their uncacheable traffic was straining my server. This will help a lot! I also added one more change to the ReadMe, it would probably save a lot of users a lot of frustration if you could include that one as well. Kind regards, |
I use sharrre a lot, and my company too, so I would be interrested in maintaining and improving the project. So if you don't have time at the moment, i could give you a hand. |
Bonjour Martin, Thank you very much for your help, I added you as a Collaborators on this repository :) |
Pourriez-vous updater le tag s'il vous plait ? Le code a changé depuis 1.3.5 mais pas le numéro de version ce qui m'a causé quelque problèmes. |
I would be interested in helping maintain sharrre. |
Hello,
I'm sorry, I don't have any time to maintain the repository so I'm looking for some people who want to maintain Sharrre :)
Julien
The text was updated successfully, but these errors were encountered: