(mainnet) migration of all ecosystems projects on DeWeb

massalabs / DeWeb

On-chain Decentralized Web Gateway

MIT License

2 stars 1 forks source link

(mainnet) migration of all ecosystems projects on DeWeb #141

Open SlnPons opened 1 month ago

SlnPons commented 1 month ago

Objective Migrate internal porjects on mainnet

How to

upload each of the project to mainnet see list here (https://github.com/massalabs/DeWeb/issues/141#issuecomment-2460035414)
add redirection to .network for all our .massa.net (centralized) domains when applicable (vesting, mns, explorer)
communicate on our ecosystem migration (commitment to decentralization)

pivilartisant commented 1 month ago

[X] create an internal list of these link // https://discord.com/channels/761151090673844244/1257281226566271096/1295742775152742421

pivilartisant commented 1 month ago

landing page MS
bridge FE
explorer FE
syntra
massa.net
massa.foundation
mns
vesting
docs

SlnPons commented 1 month ago

Who we'll pay the fees?
How we'll do that exactly?

pivilartisant commented 1 month ago

Who we'll pay the fees?

How we'll do that exactly?

also migrating once is good, but if it's better if we add github action flows to update the builds at each merge

pivilartisant commented 1 month ago

define process to add to massa provider allowlist

SlnPons commented 3 weeks ago

Who we'll pay the fees?

How we'll do that exactly?

also migrating once is good, but if it's better if we add github action flows to update the builds at each merge

What was the conclusion when we discuss this point? I can't remember

SlnPons commented 3 weeks ago

define process to add to massa provider allowlist

@thomas-senechal could you specify (again) how the allowlist will work in this 1st phase please? Because indeed, I think we should describe how it works on the doc (for our ecosystem but also for partners). wdyt?

pivilartisant commented 3 weeks ago

Who we'll pay the fees?

How we'll do that exactly?

also migrating once is good, but if it's better if we add github action flows to update the builds at each merge

What was the conclusion when we discuss this point? I can't remember

Should appear in milestone 3 roadmap as added feature

thomas-senechal commented 3 weeks ago

define process to add to massa provider allowlist

@thomas-senechal could you specify (again) how the allowlist will work in this 1st phase please? Because indeed, I think we should describe how it works on the doc (for our ecosystem but also for partners). wdyt?

Are the explainations here enough ? 🤔 https://docs.massa.net/docs/deweb/local-server-config/server-config#configuration-fields

pivilartisant commented 2 weeks ago

damip commented 23 hours ago

It would be important I think to have a CI system to automatically deploy sites on deweb from github (eg. to avoid having an older version of the docs in there)

pivilartisant commented 20 hours ago

It would be important I think to have a CI system to automatically deploy sites on deweb from github (eg. to avoid having an older version of the docs in there)

The issue is part of our milestone 3