[WIP] dev.themanaworld.org
Forum rules
This forum houses many years of development, tracing back to some of the earliest posts that exist on the board.
Its current use is for the continued development of the server and game it has always served: TMW Classic.
[WIP] dev.themanaworld.org
It's time to set up dev.themanaworld.org!
Specifications:
Hosted on Platinum
Manasource server/client
dev.themanaworld.org DNS name
You have to be able to walk around and chat to people
First map to be a small square map of about 50 x 50 tiles using current CR1 WIP ground tiles only
Playerset to be replaced by an empty (invisible) sprite for now
No equipment yet
An update server to be set up to provide all client content for it
I will be the sole dictator on who gets access to it (I'll be rather lenient towards all CR1 contributors on this)
Yes, it will be a humble start, but it will finally be a start. I feel it will be more motivating for contributing people to be able to pop quickly online to see the fruits of their work. It will also be about the only way to sensibly test amongst our group the gameplay mechanics and concepts.
So, who will take this task? Freeyorp? Jax? A group of people? Who will negotiate with Platyna about hosting this?
Specifications:
Hosted on Platinum
Manasource server/client
dev.themanaworld.org DNS name
You have to be able to walk around and chat to people
First map to be a small square map of about 50 x 50 tiles using current CR1 WIP ground tiles only
Playerset to be replaced by an empty (invisible) sprite for now
No equipment yet
An update server to be set up to provide all client content for it
I will be the sole dictator on who gets access to it (I'll be rather lenient towards all CR1 contributors on this)
Yes, it will be a humble start, but it will finally be a start. I feel it will be more motivating for contributing people to be able to pop quickly online to see the fruits of their work. It will also be about the only way to sensibly test amongst our group the gameplay mechanics and concepts.
So, who will take this task? Freeyorp? Jax? A group of people? Who will negotiate with Platyna about hosting this?
This message used to be meaningful.
Re: [REQ] dev.themanaworld.org
I propose Crush, Jaxad and me!
Of course Crush and Jaxad will have to agree!
Personally, I'm fine if the dev.themanaworld.org is hosted by Platyna as long as we can administrate it, for server maintenance tasks.
As for the rest, I'm already preparing a sample map I wanted to make run on my own server:
http://gitorious.org/tmwdata/bertram-ex ... -mana-data
http://gitorious.org/~bertram/tmwserv-d ... aserv-data
We could create repo for CR1 data, both for client and server, couldn't we?
Regards.
Of course Crush and Jaxad will have to agree!
Personally, I'm fine if the dev.themanaworld.org is hosted by Platyna as long as we can administrate it, for server maintenance tasks.
As for the rest, I'm already preparing a sample map I wanted to make run on my own server:
http://gitorious.org/tmwdata/bertram-ex ... -mana-data
http://gitorious.org/~bertram/tmwserv-d ... aserv-data
We could create repo for CR1 data, both for client and server, couldn't we?
Regards.
Re: [REQ] dev.themanaworld.org
I'd like to keep all the repos under the TMW project, instead of separate projects for each.Bertram wrote:I propose Crush, Jaxad and me!
Of course Crush and Jaxad will have to agree!
Personally, I'm fine if the dev.themanaworld.org is hosted by Platyna as long as we can administrate it, for server maintenance tasks.
As for the rest, I'm already preparing a sample map I wanted to make run on my own server:
http://gitorious.org/tmwdata/bertram-ex ... -mana-data
http://gitorious.org/~bertram/tmwserv-d ... aserv-data
We could create repo for CR1 data, both for client and server, couldn't we?
Regards.
Re: [REQ] dev.themanaworld.org
Hi Jaxad,
Does it mean you agree about my proposal?
Feel free to create whatever relevant (tmw-data-cr1/tmwserv-data-cr1?) in order to begin porting things there.
I'd also like to see a branding created in the client data from the start, once we've got a dev.themanaworld.org.
Cheers!
No problem, my repo was aimed at making own experiments only.I'd like to keep all the repos under the TMW project, instead of separate projects for each.
Does it mean you agree about my proposal?
Feel free to create whatever relevant (tmw-data-cr1/tmwserv-data-cr1?) in order to begin porting things there.
I'd also like to see a branding created in the client data from the start, once we've got a dev.themanaworld.org.
Cheers!
Re: [REQ] dev.themanaworld.org
We'll have this setup (most likely):Bertram wrote:Feel free to create whatever relevant (tmw-data-cr1/tmwserv-data-cr1?) in order to begin porting things there.
- Client
- Dev
- Test
- Prod
- Sever
- Dev
- Test
- Prod
Branding for what? Mana branding is already in a repo.Bertram wrote:I'd also like to see a branding created in the client data from the start, once we've got a dev.themanaworld.org.
Re: [REQ] dev.themanaworld.org
To formalize the effort, and since you seem to be about the only one to know what really go where.
Could you refresh my mind?
We'll have this setup (most likely):
* Client
1. Dev: git repo, update server?
2. Test: idem
3. Prod
* Server
1. Dev: git repo, server?
2. Test: idem
3. Prod
Thanks in advance.
Could you refresh my mind?
We'll have this setup (most likely):
* Client
1. Dev: git repo, update server?
2. Test: idem
3. Prod
* Server
1. Dev: git repo, server?
2. Test: idem
3. Prod
A branding for TMW, not mana which is generic. This forum is about that specific game even if we all tend to forget about it.Branding for what? Mana branding is already in a repo.
Thanks in advance.
Re: [REQ] dev.themanaworld.org
Like I said, we already have a repo for this: http://gitorious.org/tmw/tmw.Bertram wrote:A branding for TMW, not mana which is generic. This forum is about that specific game even if we all tend to forget about it.Branding for what? Mana branding is already in a repo.
Re: [REQ] dev.themanaworld.org
About access, Platinum regulations clearly define that sharing the local access (it means ssh/ftp/mail etc.) to an account is forbidden, as I have exclusive right to limit access to my property, however I may agree that a certain person will also have the access if asked, there usually were no problems with this.
Regards.
Regards.
Re: [REQ] dev.themanaworld.org
We'll want each account to have atleast two or three people with access to them (redundancy and all).Platyna wrote:About access, Platinum regulations clearly define that sharing the local access (it means ssh/ftp/mail etc.) to an account is forbidden, as I have exclusive right to limit access to my property, however I may agree that a certain person will also have the access if asked, there usually were no problems with this.
Regards.
Re: [REQ] dev.themanaworld.org
About the GIT repositories used:
Is this ok? Could we fill/discuss the gaps?
* Client
1. Dev: http://gitorious.org/mana/mana
2. Test: http://gitorious.org/tmw/tmw
3. Prod: http://gitorious.org/tmw/mainline
* Client data:
1. CR1: ?
2. tA-test (future CR test): ?
3. tA-prod (future CR prod): http://gitorious.org/tmwdata/mainline
* ManaServ Server development
1. Dev: http://gitorious.org/mana/manaserv
2. Test: ?
3. Prod: ?
* ManaServ Server-data
1. Dev: ?
2. Test: ?
3. Prod: http://gitorious.org/tmwserv-data/mainline
Best regards.
Is this ok? Could we fill/discuss the gaps?
* Client
1. Dev: http://gitorious.org/mana/mana
2. Test: http://gitorious.org/tmw/tmw
3. Prod: http://gitorious.org/tmw/mainline
* Client data:
1. CR1: ?
2. tA-test (future CR test): ?
3. tA-prod (future CR prod): http://gitorious.org/tmwdata/mainline
* ManaServ Server development
1. Dev: http://gitorious.org/mana/manaserv
2. Test: ?
3. Prod: ?
* ManaServ Server-data
1. Dev: ?
2. Test: ?
3. Prod: http://gitorious.org/tmwserv-data/mainline
Best regards.
Re: [REQ] dev.themanaworld.org
Dev/test/prod for client data and server data is what I'm after.
What does the client code repo have anything to do with this? For clients we will upon release state which is an officially supported client version.
What does the client code repo have anything to do with this? For clients we will upon release state which is an officially supported client version.
This message used to be meaningful.
Re: [REQ] dev.themanaworld.org
No. Why do we need to maintain client and server binary repos? Mana makes the binaries. The tmw/tmw repo is for our branding. The tmw/mainline repo and tmwserv project sre to be deleted.Bertram wrote:* Client
1. Dev: http://gitorious.org/mana/mana
2. Test: http://gitorious.org/tmw/tmw
3. Prod: http://gitorious.org/tmw/mainline
* ManaServ Server development
1. Dev: http://gitorious.org/mana/manaserv
2. Test: ?
3. Prod: ?
Once again, for the CRs, etc, I'd rather have everything under the tmw project. The various separate projects for eAthena stuff was done when Gitorious was setup differently. Now, we can (and should) have everything under one project: tmw.Bertram wrote:* Client data:
1. CR1: ?
2. tA-test (future CR test): ?
3. tA-prod (future CR prod): http://gitorious.org/tmwdata/mainline
* ManaServ Server-data
1. Dev: ?
2. Test: ?
3. Prod: http://gitorious.org/tmwserv-data/mainline
Re: [REQ] dev.themanaworld.org
Okay.
Could you propose a small organisation map for reference purpose?
Thanks in advance
Could you propose a small organisation map for reference purpose?
Thanks in advance
Re: [REQ] dev.themanaworld.org
tmw/client-dev
tmw/client-test
tmw/client (prod)
tmw/server-dev
tmw/server-test
tmw/server (prod)
Test and prod can likely be merged, as they are both restricted access. The dev branches have open access.
tmw/client-test
tmw/client (prod)
tmw/server-dev
tmw/server-test
tmw/server (prod)
Test and prod can likely be merged, as they are both restricted access. The dev branches have open access.