You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello @Boreal,
I'd like to improve the Eqpress API. For for what is my understanding, currently the /var/www/easypress.ca contains the deployment API.
To make the code and platform more undertandable, I suggest and would like to refactor the easypress.ca in something like eqpress-api.
Is my assumptions correct and do you agree with the refactoring?
Thanks
Adriano
The text was updated successfully, but these errors were encountered:
Hi @acataluddi - welcome, and thanks for your interest in our project!
I'd be interested to hear some more details about the refactoring you want to do. Is it just to remove references to the "easypress" name (which was the old name for EQPress before we started working on it at eQualit.ie), or do you have something more in mind? If you can explain a bit further we can figure out how best to support your efforts.
@RamJett and @kheops2713 are the people at equalit.ie who look after EQPress currently. They should be able to help with any technical questions.
Hello Richard,
for now I'm just analyzing the platform and I find confusing that a deployment code could be located in a path like /var/www/easypress.ca also because it can be easily confused with a deployed website (and removed by mistake).
Honestly I currently don't have a new architecture design to suggest, just little improvements like this.
Hello @Boreal,
I'd like to improve the Eqpress API. For for what is my understanding, currently the
/var/www/easypress.ca
contains the deployment API.To make the code and platform more undertandable, I suggest and would like to refactor the
easypress.ca
in something likeeqpress-api
.Is my assumptions correct and do you agree with the refactoring?
Thanks
Adriano
The text was updated successfully, but these errors were encountered: