multiple domains under one account

[mpower]

Hello,

I'm happy 1.8.1 came out. But i still would like to push "urge" the ability to host/park more than one domain under one account. I hope this is done soon ;)
No bother at all, just pondering..

[pascal]

yep I think we are few like that :)

For me I'm waiting :
- multiple domain hosting
- multi langage
- and the great Backup/restore tool

When I'll have that it will be really more easy to sell it in france :-p

[mpower]

couldn't agree any better myself. once those features are made available, than we can really compare interworx with the "big boys". We lack nothing important except those listed above. They must be a standard IMHO

[ximian]

yep I think we are few like that :)

For me I'm waiting :
- multiple domain hosting
- multi langage
- and the great Backup/restore tool

When I'll have that it will be really more easy to sell it in france :-p

+ one on that! :)

regards
Francisco

[Justec]

Hello,

I'm happy 1.8.1 came out. But i still would like to push "urge" the ability to host/park more than one domain under one account. I hope this is done soon ;)
No bother at all, just pondering..
I know you can park domains from SiteWorx, it's called "Pointer Domains". As to hosting multiple websites under one account, that sounds like a "reseller account" which I believe they are working on.

[pascal]

It is not forcing an reseller account.
I have some customers who have several domains (see much) and as I propose hosting with much disk space it rather becomes more interesting for them to have only one hosting account with all their domains than an hosting account per domain.

Is it possible of "wildcard" the domains and to create domains aliason the same account?

I'm thinking about a Web redirection project.

Thanks for your help
Pascal

[IWorx-Bojan]

Hello, all,

All those features are coming up soon. The multi language support should be made available in the next release of InterWorx as well as the backup/restore tool. Not sure about multi domain hosting. I will let Chris talk about that.

Cheers,

[pascal]

Hi

Ok What I know about the web redirection is :
- use of apache "VirtualDocumentRoot"
- An alias domain with wildcard
- Have an A record (in named) corresponding to "*" for this domain

For example I know that with named I only have to edit my /var/named/toto.com.hosts and add a line like this one

* IN A 153.153.153.153

But with tinydns I don't know how to do that


For the apache conf I only have to edit the file and add :

ServerAlias toto.com *.toto.com


and for the document root I'm not sure if I have to use the VirtualDocumentRoot or only the DocumentRoot as

[VirtualDocumentRoot] [DocumentRoot] /home/toto/toto.com/html/


And after only have a frame with the website as element and a pub banners

Do you know if it is enough ?

I have looked on the web but didn't find anything about this, do you know a website about web redirection ?

Thanks

[mpower]

as far as i know, you can park the domains like the previous user stated above, but hosting several domains under one account is not possible right now. It would be nice to have that feature like i said above. Most clients have more than one domain and it's not very efficient to login/out of each individual domain.

Chris does hosting, how do you handle this chris? Do you have a personal hack for your clients to hose more than one domain under one hosting plan?
It seems to me this would be a great upgrade:)

[timryberg]

as far as i know, you can park the domains like the previous user stated above, but hosting several domains under one account is not possible right now. It would be nice to have that feature like i said above. Most clients have more than one domain and it's not very efficient to login/out of each individual domain.

Chris does hosting, how do you handle this chris? Do you have a personal hack for your clients to hose more than one domain under one hosting plan?
It seems to me this would be a great upgrade:)

Nexcess.net does not use SiteWorx as we know it. They use something *much* older. The code is very different and adding the same functionality to this version requires a significang rewrite of the code, if I understood him corectly. He and I've had this conversation a couple times before and I know the featue is on the way. It's the main point of having the path to our web files so long.

/home/domaintl/domain.tld/html/

to allow for more than one domain in the same account like so:

/home/domaintl/domain.tld/html/
/home/domaintl/domain2.tld/html/

Just give them time, guys. Backup/restore is almost done and Spam/Virus is a priority because it's a security issue, IMHO.

[mpower]

Nexcess.net does not use SiteWorx as we know it. They use something *much* older. The code is very different and adding the same functionality to this version requires a significang rewrite of the code, if I understood him corectly. He and I've had this conversation a couple times before and I know the featue is on the way. It's the main point of having the path to our web files so long.

/home/domaintl/domain.tld/html/

to allow for more than one domain in the same account like so:

/home/domaintl/domain.tld/html/
/home/domaintl/domain2.tld/html/

Just give them time, guys. Backup/restore is almost done and Spam/Virus is a priority because it's a security issue, IMHO.

I dont see anyways they can have:
/home/domain/domain.tld/html
and have another
/home/domain/bla

b/c the /domain/ appends to domain.com or

I can see:
/home/domain/domain1/domain.tld/html
/home/domain/domain2/domain.tld/html

Than again, i'm just guessing/assuming. I just can't wait till they come out- i'll be the happest kid around the block:)

[timryberg]

I dont see anyways they can have:
/home/domain/domain.tld/html
and have another
/home/domain/bla

b/c the /domain/ appends to domain.com or

I can see:
/home/domain/domain1/domain.tld/html
/home/domain/domain2/domain.tld/html

Than again, i'm just guessing/assuming. I just can't wait till they come out- i'll be the happest kid around the block:)

You're making this harder than it is going to be I think

/home/domaintl/domain.tld/html/
/home/domaintl/domain2.tld/html/

is much more complicated and if I understood him corectly this is how it iwll be implemented, but as I said the coding takes time.

[Justec]

You could always edit the domain.com.conf files yourself to add more virtual host to one siteworx account, but if you want to have seperate email accounts for each domain and stuff like that you would have to do a lot more work

If you want to just host multiple websites under one account you can just do something like this:

DO THIS AT YOUR OWN RISK

First I would create the main siteworx account for Client1 and domain1. Then you would need to shell in and create a directory for domain2 under this clients folder. I would do it by copying the first domain directory and renaming it.

$ cd /home/client1
$ cp -R domain1.com domain2.com


Then you would need to edit the Vhost file (/etc/httpd/conf.d/domain1.com.conf)

#Client1 Vhost file

#domain1
#This will already be created for you when you create your SiteWorx Account
<VirtualHost 111.222.333.444:80>

ServerName domain1.com
DocumentRoot /home/client1/domain1.com/html/

# Other code below
</VirtualHost>

#domain2
#This VirtualHost code here you will have to add yourself
<VirtualHost 111.222.333.444:80>

ServerName domain2.com
DocumentRoot /home/client1/domain2.com/html/

# Other code below
</VirtualHost>


Then an apachectl -k graceful and that should be it.

This would solve the problem, although not the easiest way. Also, I do not know how this would affect the bandwidth monitoring and stats.

If it's not that important you best bet is to wait for InterWorx features that handle this.

[timryberg]

This would solve the problem, although not the easiest way. Also, I do not know how this would affect the bandwidth monitoring and stats.

If it's not that important you best bet is to wait for InterWorx features that handle this.

Doing this would probably _work_ but the changes would not show up in SiteWorx since siteworx used a database to keep track of all of that stuff and this would not show up in that database. The same os true for turning on/off cgi from the raw files, etc.

Someone from InterWorx feel free to corect me if I am wrong.

[IWorx-Chris]

Lots to respond to here :), and I'm finally back posting after a few week absense!

- Regarding multi-domain

It's designed into iworx-cp, just not tested/finished. Tim is right that the reason the paths are so long is to allow a single account with many domains. The nice thing about the design we have is that you will be able to have a "master" domain that can FTP to all "slave" domains (i.e. you login to ftp at the /home/<user> level and can see all domains you own). Sites will be setup at /home/<user>/domain1.com, /home/<user>/domain2.com etc.

THERE IS NO ETA ON THIS, BUT IT IS IN THE WORKS.

- Multi-lang

This is in 1.9.0 (the next release) and from what I've seen lately it's 95% done.

- Backup / Restore of SiteWorx Accounts

This is in 1.9.0 and again, from what I've seen is 90% done.

- Regarding what we (NEXCESS.NET) do for multi-domain and/or multi-account clients.

We hacked an ancient (3.1.x) version of modernbill many moons ago to show clients all of their domains in a single spot within the MB interface. We also gave them 'one click' access to these (mega-old-style) SiteWorx accounts. A few things to note: I often likve having clients who have multiple sites on different servers (even at different DCs) since it spreads your net client load around. If a given DC has issues your clients are less likely to complain (and more likely to believe your downtime diagnosis) if some of their sitse are up and some are down. I only add this since we don't really do 'multi-domain hosting' and what we do is more 'multi-account' hosting.

- Regarding Justin's Solution

It will work in that you'll have the 2 accounts setup and accessible via web/ftp but SiteWorx won't understand the 2nd account exists so you'll loose some SiteWorx features (mail, bw tracking etc). But it won't "hurt" anything per se.

Let me konw if I missed anything.

Chris

[mr_dizzle]

any news on "multiple domains" under one account?

[timryberg]

any news on "multiple domains" under one account?

Isn't that part of the reseller panel with 2.0?

[IWorx-Chris]

Regarding multi-domains we are planning it for the 2.0 release I HOPE. This is 2 releases out. We're at work on resellers right now for the release-after-next and multi-domain is next on (my) list of "big features" to implement. No promises on timing, but just FYI.

Chris

[timryberg]

Thanks for the update, Chris. I know a lot of people who are looking foreward to that partucular feature. We may be able to lure a few people away from the competition when that is available :-)

[mr_dizzle]

any updates on this? this is the one thing holding me back from going with interworx

[IWorx-Chris]

any updates on this? this is the one thing holding me back from going with interworx


I don't have a timeline mr_dizzle. It is on our high priority list but it's also a non-trivial problem. Sorry to be so vague but I don't want to lead anyone on that it's around the corner. It's going to be a few months (at least) until we have a production setup that is usuable by all.

Chris

[Roman2K]

I think it's better to have one SiteWorx for one website which can have subdomains and pointer domains because the statistics reflect only this website and if we have several websites on one siteworx account, the statistics will not reflect the usage of each website but all hosted ones.

It's good to be able to create a reseller account for multiple SiteWorx account per customer, but it would be great if we could transfer an existing SiteWorx account to a newly created reseller. I don't think it's possible for now. If no : is it planed ?

[timryberg]

I think it's better to have one SiteWorx for one website which can have subdomains and pointer domains because the statistics reflect only this website and if we have several websites on one siteworx account, the statistics will not reflect the usage of each website but all hosted ones.



Actually, I think that depends on how they code it. A very basic setup would work that way, but I don't think that is what Chris means. As I understand it the plan is to make each domain fully functional and independent: httpd, databases, email, dns, logs, stats, etc. But owned by the same Linux user for file quota purposes. That's part of why it is taking so long. If all you want is to add a new web domain (with no other features) to an account that can be done now with a little bit of manual copying and editing of your Apache virtual host config file. I did actually do this a few versions back just to see if it would work, and it did (sort of), but I haven't tested it on the 2.x setup.



It's good to be able to create a reseller account for multiple SiteWorx account per customer, but it would be great if we could transfer an existing SiteWorx account to a newly created reseller. I don't think it's possible for now. If no : is it planed ?

It's not possible withthe current 2.0.5 release, not sure about the upcoming 2.1.0. I do know Paul said it was on the way. As of right now if you want to do this you need to backup the SiteWorx acount using the backup utility, log into the Reseller account in NodeWorx [I]and Import the backup you just made (NOTE: Paul cautioned that you test it with a test account before actually doing this just to make sure things go smoothly since you would need to delete the original account before you would be able to import the new.]

[Roman2K]

Actually, I think that depends on how they code it. A very basic setup would work that way, but I don't think that is what Chris means. As I understand it the plan is to make each domain fully functional and independent: httpd, databases, email, dns, logs, stats, etc. But owned by the same Linux user for file quota purposes. That's part of why it is taking so long. If all you want is to add a new web domain (with no other features) to an account that can be done now with a little bit of manual copying and editing of your Apache virtual host config file. I did actually do this a few versions back just to see if it would work, and it did (sort of), but I haven't tested it on the 2.x setup.
Ok. It would be excellent if it is planed to do as you said :). Indeed, I didn't think about emails, dns etc...


It's not possible withthe current 2.0.5 release, not sure about the upcoming 2.1.0. I do know Paul said it was on the way. As of right now if you want to do this you need to backup the SiteWorx acount using the backup utility, log into the Reseller account in NodeWorx [I]and Import the backup you just made (NOTE: Paul cautioned that you test it with a test account before actually doing this just to make sure things go smoothly since you would need to delete the original account before you would be able to import the new.]

Yeah good idea this backup/restore tip ! Thank you :).

[timryberg]

Ok. It would be excellent if it is planed to do as you said :). Indeed, I didn't think about emails, dns etc....

The InterWorx developers don't believe in doing things half way. One thing Chris told me ages ago is that they were trying to take the most important features of the competing panels and do them better.

From what I've seen this is eactly what they do. Once in a while a high demand feature is released in a more basic form and then redone later with better features (e.g. the Backup Restore was limited in 1.9.0 but became more feature packed in 1.9.3) but usually this is the exception, not the rule.

If you want to know how I added a domain to a siteworxk acount (website only) then feel free to ask. It wasn't too complicated but did require some file editing.

[Roman2K]

The InterWorx developers don't believe in doing things half way. One thing Chris told me ages ago is that they were trying to take the most important features of the competing panels and do them better.

From what I've seen this is eactly what they do.
I believe in that !!! When I tested NodeWorks / SiteWorks I was extremely impressed and felt in love of it...
In fact for now I'm doing free webhosting with a panel I wrote and it goes well but I would like a cleaner, faster (my background scripts make the old server suffering), more complete and that gives me a full control of the server behind a single web interface : it looks to be the case with IWorx. What more people look happy with it and there is a good support so a webhosting panel could difficultly be better :D.

If you want to know how I added a domain to a siteworxk acount (website only) then feel free to ask. It wasn't too complicated but did require some file editing.
Yes I would like to know, even if I won't do this.

I have another question : once I have bought a IWorx licence, must I buy another one if I want to install it on another server ?

[IWorx-Socheat]

I have another question : once I have bought a IWorx licence, must I buy another one if I want to install it on another server ?

If you are going to run two separate servers, both with IWorx-CP on them, then yes, you'll need to be another license.

However, if you're just moving from one to hte other, and will only have one server with IWorx-CP then no, you do not need to purchase another license. You will need to give us the new IP of the new server, so we can transfer your license.

[Roman2K]

Ok thank you :).