So, I got a basic Gitea Instance here: https://git.cowdev.online, but I would like to rename my site.
NOTE: It's actually a Nginx server which uses a Gitea Server on port 3000 as a reverse proxy.
If the website goes down, It's most likely I'm just playing with it or my Server trial or Domain ended.
UPDATE: I upgraded to GitLab, So you can't use the link anymore.
Found the solution, there's a property in gitea's config file (for me located in /var/snap/gitea/gitea-common/gitea.ini)
Related
In the office, we have already setup a redirect in the DNS to push .dev back to the localhost. The issue is when I am not in the office this does not work. I edited my host file for the websites but as I add more in the future I would prefer to not have to edit my host file.
Is there a way, within my computer, that I can force the TLD of .dev to always go back to my localhost?
I realize I may have to find a way to do this on my router so that the DNS is resolved.
Example:
- Local IIS
-- Website A (with a Host Name Binding of website-a.dev)
-- Website B (with a Host Name Binding of website-b.dev)
When I open a browser on my local box and type in website-a.dev, it should loop back to my local IIS and pull this website. Same thing for website-b.dev, of course, going to the other website. Now I know if at work we have setup the DNS to allow for this but I want to know if this can be done at home, where I do not have direct access to the DNS.
I know I can just put into my host file
127.0.0.1 website-a.dev
But I want a catch all for .Dev to go back to 127.0.0.1
Take a look at:
https://superuser.com/questions/135595/using-wildcards-in-names-in-windows-hosts-file
It explains that using Acrylic allows you to use wildcards and acts just like your host file.
I used Visual Studio and IIS to successfully deploy a web project to the localhost. Go to localhost on port 51? Great, it pulls up. Wonderful.
Then I tried to add a binding so I could type in "example:51" and it would pull up the website. I then got the following error in chrome:
This site can’t be reached
example’s server DNS address could not be found.
ERR_NAME_NOT_RESOLVED
Looking around, some answers said to alter the hosts file in Windows. I did that, and it solved everything. I type in "example:51", I'm directed to localhost, which pulls up the website.
Then I completely removed the "example" binding from IIS, and it still worked fine. I wasn't so much adding a binding as changing the way "example" is interpreted. It also sends me to localhost on every other port as well, including 80, which I don't think a binding would have done.
So now I'm thinking I didn't solve the bindings problem correctly. Should I have done something differently?
IIS bindings tell IIS how to respond when it receives a request for a specific hostname.
You probably have IIS configured to respond with your site regardless of hostname, so that doesn't matter.
IIS bindings have nothing to do with DNS or name resolution, which is how the browser knows that example should resolve to your host.
yesterday I installed gitlab on a vm of mine and configured everything to work with it.
Gitlab listens on port 8081 of my domain (e.g. domain:8081).
I have an apache instance which listens to port 80 and 443, so I did a forward there (e.g. domain/git).
Everything worked fine (except the css theme of domain/git, but thats no problem), but then I changed the root url (I think, I don't know how this settings is called) in the admin section directly in gitlab to http://domain/git to let gitlab show me directly this url if I want to copy a URL to clone.
Now I can't access my gitlab instance, because I do have an redirection loop.
I also can't find where the setting was done by gitlab itself, I guess it's stored in the database and not any file.
Can someone help me figure out how to change this particular configuration back to default?
Thanks in advance!
You likely changed the 'homepage url' used for redirecting logged out users. Instead of hitting the domain mainpage, hit /users/sign_in and you should be able to sign back in as your admin user. Go to the admin section, and clear out the setting.
You instead need to go into your config/gitlab.yml (source install) or /etc/gitlab/gitlab.rb (package install) and set the external_url to be the address you wanted.
Then restart/reconfigure the app to have it used in the git clone instructions.
What's required to setup Neo4j behind IIS proxy server?
I am running into the issue listed here: https://github.com/neo4j/neo4j/issues/112
Error message (Chrome console):
displayed insecure content from =1363713541737">http://xyz:7474/db/data/?=1363713541737
xyz is the server name.
Thanks
Considering the GitHub issue is still open, you can assume that this is not currently supported and no workaround has been supplied by Neo.
If you want to persist ahead, you will need to rewrite the content passing through the proxy.
This is a fairly simple question (in my opinion) but for some reason despite my Googling I cannot find a straight answer to it.
Currently I have an application running under my Default Web Site located at http://localhost/myApp. Ideally, I'd like to create a new site in IIS with a binding to 127.0.0.1:80 and a host header of http://myApp so that I can test my url rewriting rules properly (since my app will ultimately be hosted at http://www.myApp.com, not http://www.somedomain.com/myApp).
So, my question is this: will the above work? I haven't had a chance to try it yet.
If the above will not work, what are the steps to be able to access my site at http://myApp on my local network?
It should work provided you fool the OS into resolving www.myapp.com to 127.0.0.1. To do so, edit your hosts file in %systemroot%\system32\drivers\etc to contain the following:
127.0.0.1 myapp.com
I believe you could do just myapp(without the .com) as well, but that gets a bit trickier because how that is resolved depends on your node type. (hybrid, etc) To be safe, add
127.0.0.1 myapp
to BOTH the hosts and LMHosts files in the same directory. By default the lmhosts is non-existent and there is a lmhosts.sam there. You'll have to rename that to just lmhosts or create a new one.
Then create the binding as per usual in IIS7/7.5 (I assume it's 7... Site->Actions->Bindings->Add or Edit->Populate hostname accordingly).. IIS6 will work too but it's alot harder to get https working should you need it.