archethic-node
archethic-node copied to clipboard
archethic-foundation
Webhosting
Is your feature request related to a problem?
Today, a transaction for hosting is an object with a liste of files as attributes. This approach doesn’t allow to add additional information
Describe the solution you'd like
The proposal is to have an object with metadata and an attribut such as ‘files’ with the same content as today.
So we can have additional fields like name/description, author etc.., ability to add headers in the response,… eventually an attribut having the address on a transaction containing a certificate (if https managed by Phoenix/elixir and not Nginx. Etc..) Can specify the type site, lib (can be shared by other website) etc
Additional context
No response
Hello @gvqualite Thanks for the contribution.
Could you give more information or details how do you think of usage of those additional fields like name/description/author ?
Hello Samuel,
By specifying a name/description/author/version/url etc.. of the site/package, people can see what's the content and we can imagine that these information car be used to build a search engine/marketplace/package directory(ala npm)
For example for a library such as JQueryUI, we can have { "name":"JQuery UI", "version":"1.13.1", "date":"20 January 2022", "description":"jQuery UI is a curated set of user interface interactions, ...", "url":"http://jqueryui.com/", "developers":"Paul Bakaus · Scott González · Jörn Zaefferer ·", "type:"Plugin", "license":"MIT License", "support:"[email protected]", "files": { "/jqueryui/jquery-ui.css": ............, "/jqueryui/jquery-3.6.0.js": ............, "/jqueryui/jquery-ui.js": ............, }
}
For Web site, he can be interesting to have also a few of these static information, including the URL of the site.
It is important to standardize attributes to avoid multiple names for the same item (via AEIP?)
Trough metadata we can provide some information to the web hosting server. I mentioned the certifcate (address of the transaction) for supporting HTTS with a custom name, but also to indicate a list of headers that must be added (statically) by Archtethic on each response. Need to have also the capability to remove headers, or limit thru IP addresses etc...
I think that there is a lot of use case, not listed there about the capability to set Web hosting mechanism (need to check on website server solutions)
Hop that this will help
Best Regards Philippe
Forgot also that logs are important for website (not only Google system), may be we can add in meta data a remote log service for storing all cals, as no need to store this in the blockchain.
