Intranet suggestions....
-
@stacksofplates said in Intranet suggestions....:
@nashbrydges said in Intranet suggestions....:
Any of these options recommended for a multi-client scenario? Would need authentication so each client only accesses their own documentation.
Yes drupal can do that. Wiki.js can have roles and users that have access to specific areas but I've noticed if you search for something, the search show up in the bar from areas they don't have access to. They can't get there, but the titles and such show up.
Yeah, can't have search results show up for another client, even if inaccessible. Thanks for this tidbit of info on wiki.js.
-
@stacksofplates said in Intranet suggestions....:
@nashbrydges said in Intranet suggestions....:
Any of these options recommended for a multi-client scenario? Would need authentication so each client only accesses their own documentation.
Yes drupal can do that. Wiki.js can have roles and users that have access to specific areas but I've noticed if you search for something, the search show up in the bar from areas they don't have access to. They can't get there, but the titles and such show up.
Search is so often a week point in security, argh. If all you are doing is hiding passwords or details, it often works fine. If you are hiding concepts, it's useless.
-
@scottalanmiller said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@nashbrydges said in Intranet suggestions....:
Any of these options recommended for a multi-client scenario? Would need authentication so each client only accesses their own documentation.
Yes drupal can do that. Wiki.js can have roles and users that have access to specific areas but I've noticed if you search for something, the search show up in the bar from areas they don't have access to. They can't get there, but the titles and such show up.
Search is so often a week point in security, argh. If all you are doing is hiding passwords or details, it often works fine. If you are hiding concepts, it's useless.
Ya I was really disappointed when I saw that. So you need multiple sites for separation, which sucks.
-
@stacksofplates said in Intranet suggestions....:
@scottalanmiller said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@nashbrydges said in Intranet suggestions....:
Any of these options recommended for a multi-client scenario? Would need authentication so each client only accesses their own documentation.
Yes drupal can do that. Wiki.js can have roles and users that have access to specific areas but I've noticed if you search for something, the search show up in the bar from areas they don't have access to. They can't get there, but the titles and such show up.
Search is so often a week point in security, argh. If all you are doing is hiding passwords or details, it often works fine. If you are hiding concepts, it's useless.
Ya I was really disappointed when I saw that. So you need multiple sites for separation, which sucks.
Is it still an issue if Wiki.js is not setup for public access?
-
@black3dynamite said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@scottalanmiller said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@nashbrydges said in Intranet suggestions....:
Any of these options recommended for a multi-client scenario? Would need authentication so each client only accesses their own documentation.
Yes drupal can do that. Wiki.js can have roles and users that have access to specific areas but I've noticed if you search for something, the search show up in the bar from areas they don't have access to. They can't get there, but the titles and such show up.
Search is so often a week point in security, argh. If all you are doing is hiding passwords or details, it often works fine. If you are hiding concepts, it's useless.
Ya I was really disappointed when I saw that. So you need multiple sites for separation, which sucks.
Is it still an issue if Wiki.js is not setup for public access?
Yes because you don't want clients seeing info for other clients. And we were going to use it for a user area and an internal documentation site. But that won't work now.
-
@scottalanmiller said in Intranet suggestions....:
@black3dynamite said in Intranet suggestions....:
@scottalanmiller said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@jaredbusch said in Intranet suggestions....:
@zachary715 said in Intranet suggestions....:
@fuznutz04 said in Intranet suggestions....:
I'm still evaluating https://wiki.js.org/. I have it installed and setup, and I love the interface, but have not had a lot of time to really test it out in a production environment yet.
Wordpress is definitely a solid choice, especially with the right plugins.
I've been playing with https://wiki.js.org/ as well and I'm really loving it. It's still fairly young it seems but looks promising. Been spending a lot of time migrating notepad and word file documentation to it over the last week or two.
I also use Wordpress for a personal website, and would recommend it if you're needing additional functionality that a wiki may not offer.
ok, damnit. now I really need to set this up.
Ya it's pretty cool. It's awesome that it auto commits to a Git repo.
Yeah, we have been using it a little bit. It is what we are replacing Sharepoint with.
Easy to setup? What OS are you using?
Not my first choice, but it is on CentOS 7 shared with some other workloads.
I will be trying it on OpenSuse. My preferred Linux server distro.
-
@penguinwrangler said in Intranet suggestions....:
@scottalanmiller said in Intranet suggestions....:
@black3dynamite said in Intranet suggestions....:
@scottalanmiller said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@jaredbusch said in Intranet suggestions....:
@zachary715 said in Intranet suggestions....:
@fuznutz04 said in Intranet suggestions....:
I'm still evaluating https://wiki.js.org/. I have it installed and setup, and I love the interface, but have not had a lot of time to really test it out in a production environment yet.
Wordpress is definitely a solid choice, especially with the right plugins.
I've been playing with https://wiki.js.org/ as well and I'm really loving it. It's still fairly young it seems but looks promising. Been spending a lot of time migrating notepad and word file documentation to it over the last week or two.
I also use Wordpress for a personal website, and would recommend it if you're needing additional functionality that a wiki may not offer.
ok, damnit. now I really need to set this up.
Ya it's pretty cool. It's awesome that it auto commits to a Git repo.
Yeah, we have been using it a little bit. It is what we are replacing Sharepoint with.
Easy to setup? What OS are you using?
Not my first choice, but it is on CentOS 7 shared with some other workloads.
I will be trying it on OpenSuse. My preferred Linux server distro.
Leap or Tumbleweed type of user?
-
@black3dynamite Tumbleweed
-
-
@penguinwrangler said in Intranet suggestions....:
@black3dynamite Tumbleweed
Any cool how to guides that you might like to share here? CentOS and now Fedora is pretty much the goto here.
-
@black3dynamite said in Intranet suggestions....:
@penguinwrangler said in Intranet suggestions....:
@black3dynamite Tumbleweed
Any cool how to guides that you might like to share here? CentOS and now Fedora is pretty much the goto here.
I guess I could. I haven't installed https://wiki.js.org/ yet on it. I will report back once it is up.
-
@stacksofplates said in Intranet suggestions....:
@black3dynamite said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@scottalanmiller said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@nashbrydges said in Intranet suggestions....:
Any of these options recommended for a multi-client scenario? Would need authentication so each client only accesses their own documentation.
Yes drupal can do that. Wiki.js can have roles and users that have access to specific areas but I've noticed if you search for something, the search show up in the bar from areas they don't have access to. They can't get there, but the titles and such show up.
Search is so often a week point in security, argh. If all you are doing is hiding passwords or details, it often works fine. If you are hiding concepts, it's useless.
Ya I was really disappointed when I saw that. So you need multiple sites for separation, which sucks.
Is it still an issue if Wiki.js is not setup for public access?
Yes because you don't want clients seeing info for other clients. And we were going to use it for a user area and an internal documentation site. But that won't work now.
I suppose I could try the multi-tenant feature in Alfresco. Not exactly what I wanted but might work.
-
@nashbrydges said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@black3dynamite said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@scottalanmiller said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
@nashbrydges said in Intranet suggestions....:
Any of these options recommended for a multi-client scenario? Would need authentication so each client only accesses their own documentation.
Yes drupal can do that. Wiki.js can have roles and users that have access to specific areas but I've noticed if you search for something, the search show up in the bar from areas they don't have access to. They can't get there, but the titles and such show up.
Search is so often a week point in security, argh. If all you are doing is hiding passwords or details, it often works fine. If you are hiding concepts, it's useless.
Ya I was really disappointed when I saw that. So you need multiple sites for separation, which sucks.
Is it still an issue if Wiki.js is not setup for public access?
Yes because you don't want clients seeing info for other clients. And we were going to use it for a user area and an internal documentation site. But that won't work now.
I suppose I could try the multi-tenant feature in Alfresco. Not exactly what I wanted but might work.
Phone might work.
https://plone.org/ -
@stacksofplates said in Intranet suggestions....:
I'll recommend Drupal. It's the most flexible and you can build anything. It's great for very simple sites or really complex ones.
I'm apparently one of the few that has much more experience with Drupal than Wordpress. Too be fair tho, when we moved to Drupal originally it was moving off of Joomla, which would make just about anything else look good by comparison.
-
@travisdh1 said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
I'll recommend Drupal. It's the most flexible and you can build anything. It's great for very simple sites or really complex ones.
I'm apparently one of the few that has much more experience with Drupal than Wordpress. Too be fair tho, when we moved to Drupal originally it was moving off of Joomla, which would make just about anything else look good by comparison.
To me it seems to get the benefits Drupal offers over Wordpress, you have to sit down and spend a lot of time coding shit. Otherwise I'd just install a plugin to Wordpress to get what I need.
-
@tim_g said in Intranet suggestions....:
@travisdh1 said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
I'll recommend Drupal. It's the most flexible and you can build anything. It's great for very simple sites or really complex ones.
I'm apparently one of the few that has much more experience with Drupal than Wordpress. Too be fair tho, when we moved to Drupal originally it was moving off of Joomla, which would make just about anything else look good by comparison.
To me it seems to get the benefits Drupal offers over Wordpress, you have to sit down and spend a lot of time coding shit. Otherwise I'd just install a plugin to Wordpress to get what I need.
That's how I feel about it Drupal too. And Wordpress is so much easier for my users too.
-
@tim_g said in Intranet suggestions....:
@travisdh1 said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
I'll recommend Drupal. It's the most flexible and you can build anything. It's great for very simple sites or really complex ones.
I'm apparently one of the few that has much more experience with Drupal than Wordpress. Too be fair tho, when we moved to Drupal originally it was moving off of Joomla, which would make just about anything else look good by comparison.
To me it seems to get the benefits Drupal offers over Wordpress, you have to sit down and spend a lot of time coding shit. Otherwise I'd just install a plugin to Wordpress to get what I need.
Everything I needed to do with Drupal, someone already had a plugin made that did it. So at least for me, it was just about the same experience. I happen to use it for my personal site because I already knew it very well. I'm sure Wordpress would be just as easy once I learned where everything was in the menus.
-
@travisdh1 said in Intranet suggestions....:
Everything I needed to do with Drupal, someone already had a plugin made that did it.
Yeah, same with WordPress... so in that case Drupal provides no benefit over WordPress, except for the fact you are more familiar with Drupal being the only reason to use it.
-
@tim_g said in Intranet suggestions....:
@travisdh1 said in Intranet suggestions....:
@stacksofplates said in Intranet suggestions....:
I'll recommend Drupal. It's the most flexible and you can build anything. It's great for very simple sites or really complex ones.
I'm apparently one of the few that has much more experience with Drupal than Wordpress. Too be fair tho, when we moved to Drupal originally it was moving off of Joomla, which would make just about anything else look good by comparison.
To me it seems to get the benefits Drupal offers over Wordpress, you have to sit down and spend a lot of time coding shit. Otherwise I'd just install a plugin to Wordpress to get what I need.
You don't need to do any coding at all. It's all built through the interface.
-
@tim_g said in Intranet suggestions....:
@travisdh1 said in Intranet suggestions....:
Everything I needed to do with Drupal, someone already had a plugin made that did it.
Yeah, same with WordPress... so in that case Drupal provides no benefit over WordPress, except for the fact you are more familiar with Drupal being the only reason to use it.
The modules in Drupal are more powerful than the plugins for WordPress. It's two different architectures. One is a blogging platform that can do static sites. The other is a CMF that you can build your own CMS or web app.
