Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

Users having their own slashcode?

posted by Krow on 02:34 PM January 11th, 2001   Printer-friendly   Email story
frank-n-f writes "Is there a way to install slashcode or configure it so that all the users on my unix system have access? For instance, how could I make it so that in each users WWW (apache) directory they could create a slash site of their own"
Depends on what you are after. Under bender each user can have a journal, which may work for what you want. You could also possibly create sections for each user and do something like what we do for slashdot.org/apache/. Restrict each new author to a given section.
Other suggestions?
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • by Anonymous Coward
    This probably wouldn't work for what this guy wants and it definitely would't work for a commercial environment. This article is definitely tied to the one a day ago about making slash easier to run in virtual hosting environments. It is also in line with my comment about how slash needs to be as much as is possible contained within individual unix accounts so that you can have 1(+) slash installs per uid, rather than per server. It's like allowing every user to run their own ircd, you don't make them all share 1 ircd and only give them their own channel do you? No. Same should be possible with slash.
  • by Anonymous Coward
    to have multiple sites with different domains on one machine with bender. I've spent the better part of yesterday and today getting bender running and messing with it on one of my boxes.
    From my limited experience with it, it looks like this next version of slash is coded to handle multiple sites far better then the 1.x series was.
  • Yes, it will be a bit easier, but only because it makes more sense and has a more automated setup. In essence, it is very similar. The one big thing that makes it "easier" is that to customize a site, all of the HTML/text is in templates, which are in the database, so you don't have to edit code to change the appearance. You just edit the templates in the database. This is one area where we will likely need the most feedback and beta testing.
  • If you were going to run a business of maintaining Slash sites, by this I mean hundreds of them, you might want to check out the new offerings in the VMware product line [vmware.com] for solutions providers. I know that sounds like a marketing flack talking, sorry.

    This would allow you to create a repeatable basic image of a Slash site and deploy it as many times as necessary. I think VMware contemplates this type of use [vmware.com], particularly of its newer product offerings.

    I have had good success using VMware for development tasks and office application use on the Windows platform, and I am seriously considering using VMware to test Bender. If you want to read more about my experiences with VMware, check out these stories on ctdata.com [ctdata.com].
    --

    Dave Aiello
    Chatham Township Data Corporation

    --

    --

    Dave Aiello
    Chatham Township Data Corporation [ctdata.com]

  • Is the intent to have slash sites with unique domain names or all under the same domain?

    I think anyway you look at it, it's going to require a person doing it. The userid and unique domain thing would be a mess. Editing Apache configs, etc. NOT something a script could do in my opinion. Atleast with the current setup of slash (the code block in the http.conf is big and you have to edit quite a few things). Unless you go with the www.domain.com/useridsection model, but that still requires someone create that section and create an author with access to that section and maybe only that section.

    If the goal is to have something where you create a user id on your unix system, then create a section (IE: www.domain.com/newuseridsection), I think doing that with like a perl script would be fairly easy.

    What it would do is ask for the newuserid, and other fields that are necessary in the AUTHORS table (like email, password, nickname, selectlevel, etc), then the section name and whether it is standalone, etc. Then it would go and insert those into the slash database, and there you go!

    I think its easier and safer to do it via a person though.
    -- It's either on the beat or off the beat, it's that easy.

    --

    --
    It's either on the beat or off the beat, it's that easy.