EventGhost

Ad blocker detected:
Our software and support is 100% free. This website is not.
You can donate in 2 ways, by turning off your ad blocker or by pressing the Donate button.

************ NOTICE ************

UPDATE YOUR BOOKMARKS!!!

We have an issue that there is no way around as of yet.
I have done all I can to try and prevent this from happening.
We are going to be losing the .com, .org and .de domains.
We have not been able to contact the original author of EventGhost
(the person that owns those domains) to redirect them to the new web server.
I set in motion when we first moved a redirection from the old server to the new server.
I also put in markers so that search engines would see this change and update any pointers
they have. We still have the .net domain for the production site. and the .rocks for the test site.
For the past few months you have been getting redirected to the .net site if you used one of the 3
domains mentioned above. I just wanted to tell everyone so they can make any changes needed.

Documentation: Has not yet been implemented. I don't see anyone volunteering to do the work of changing the help file generation and there is some controversy over removing the built-in help.

So it's clear that the only thing that still needs to be done is the documentation and that's a big task. The current documentation system works fine. It's possible for anyone to propose edits by submitting a pull request. I'm not saying that the documentation system can't be improved but I don't want to see that part of the project block the implementation of the rest of it.

So at this point I think the ball is in the court of whoever has the ability to edit the current website. I see no reason why the Home, Downloads, and Wiki can't be immediately moved over to the GitHub wiki pages. We need some communication from the decision makers. If you have any concerns or opinions about this project then please speak up.

By presenting the whole project as one package it's more likely that one controversial change would block the whole thing. It's not an all or nothing deal, the changes to each part of the website can be considered individually. I think it's obvious to everyone that the wiki is broken and something needs to be done about it so that part should have the least chance for conflict.

And the media portal plugin should be removed as well. Because it's non functional. This is due to changes in media portal and not eg. There has been a new plugin made for either end. But the included EG plugin shouldn't be there any more.

I am happy to see the Harman kardon one removed. As it does not work properly either.

kgschlosser wrote:Do me a favor. Read the description on the github wiki and tell me if the description of EventGhost makes you think that it's an automation tool for controlling Microsoft Windows.

That is just one thing that it does. But the description makes it seem limited to Windows control.

I read it as meaning that the program runs on the windows operating system. It even says that you can "turn on your lights when the sun sets".

kgschlosser wrote:
I have EventGhost monitoring my Hot tub.. LOL that has nothing to do with Windows.

You're doing the monitoring on your Windows computer.

I think the focus now should be on moving the existing content rather than modifying that content. Focus on the infrastructure changes that are being proposed. Once the transition has been made editing the content will be very easy for anyone to do. Dequi's work on the wiki should provide enough of a demonstration of the proposal for a decision maker to implement the move or express their reservations on doing so. Of course that content will be improved but until we know whether it's even going to end up being used it's not worth putting a lot of time into that.

pearbear wrote:
I think the focus now should be on moving the existing content rather than modifying that content. Focus on the infrastructure changes that are being proposed. Once the transition has been made editing the content will be very easy for anyone to do. Dequi's work on the wiki should provide enough of a demonstration of the proposal for a decision maker to implement the move or express their reservations on doing so. Of course that content will be improved but until we know whether it's even going to end up being used it's not worth putting a lot of time into that.

I get ya.. But if i don't spew it out now I will forget by time something takes place.

and I have set up a test server if it is needed. running Ubuntu, Apache, MySql, PHPMyAdmin, PHP, XRDP (with access to the unity desktop). And I have also made a duplicate of the forum database and it is already added to MySQL.

I do not know all of the back end crap to move the entire website... well I know how to get the information. but as far as how to install it into the server I do not know how..

This way there is some kind of a server system which can be tested. and make sure everything is functional. But also provides a means to go live with it to make sure there are no errors. and after a run with it if everything is good it can be moved over to the web hosting account. and in the event of a catastrophic problem, it can be switched back with little down time.

If there is any interest by the folks working on the website shoot me a PM for further information

You could see this as the home page indeed. Don't know if you can add a custom domain name to a wiki of a GitHub repository. Have not found any reference online how to do this yet but since this is a git repository should be possible no? Doing some tests on this. If not then we need to find an other way to link the EventGhost domain to the repository. We also need to consider what happens with search-engine indexed pages that wont be there anymore.

As far as linking the website to a domain. Let me handle that end of it. There is a domain of EventGhost.rocks that I can tinker with to see if I can get it pointed. I do not think this will be possible from a DNS level. Because of the fact it's not a host/domain being pointed to. It's an object on a specific server. To do a point for that would require a webserver to do the redirect.

dequi wrote:Don't know if you can add a custom domain name to a wiki of a GitHub repository. Have not found any reference online how to do this yet but since this is a git repository should be possible no? Doing some tests on this. If not then we need to find an other way to link the EventGhost domain to the repository.

Personally I don't think it's a deal breaker if the custom domain name isn't possible, though it would be better if this was somehow possible. I don't know if others would consider that a major issue. Otherwise it seems like they could just do a redirect of eventghost.org/index.html to https://github.com/EventGhost/EventGhost/wiki. Worst case scenario would be to just stick with the current home page, which wouldn't be the end of the world. I wonder if revenue loss caused by the wiki home page not having an ad would pose any problems for the financial solvency of the site? I'd assume the majority of the traffic is on the forum and I remember zian said the revenue exceeds expenses.

dequi wrote:
We also need to consider what happens with search-engine indexed pages that wont be there anymore.

I think it would be a good idea to redirect every current page to the new page on the wiki that replaces it.

dequi(and anyone else), what do you think of my proposal of immediately moving forward with the parts that are already complete? It seems like at least the Wiki page(which has been renamed "Tutorials" by dequi) and the Downloads page could be transferred over very easily.

But in all honesty I would set up an entirely different organization for the wiki, for the webpage, and for the forum because of how this works, it looks as tho you can only set one directory to be for eventghost.github.io

Keep in mind we're talking about the GitHub wiki here, not GitHub Pages(though dequi was previously proposing using GitHub Pages for the website). From what I can tell, the custom domain information is only for GitHub Pages and is not relevant to the GitHub wiki but I could be wrong about that.

well i am git-dumb and you guys are the experts on it. but all i know is that there is no way to set a CName (alias) to anything other then a host.domain. without the use of some sort of forwarding webserver