How to create mac vps (virtual private server) and access it via browser - xcode

How to create mac vps (virtual private server) and log in to it via browser, I want to be able to create environment like http://www.macincloud.com/, i have os x server but not sure how to set it up so that it can be accessed via browser, reason i'm trying to do this is to be able to use xcode from windows machine over internet.
any help is much appreciate it

I'm not sure how OSX Server works, but I believe what you want to do can be completed using a VNC.
Here is a quick tutorial I found on youtube on how to create a VNC on your mac computer so that you can control it from another computer by logging into the VNC server.
You will not be able to use your browser to log in, so you will need to download a 3rd party application (tightVNC is mentioned in the video) to access your mac remotely.
https://www.youtube.com/watch?v=13vIi37TkCg
Hope this helps!

If you requirement is something that you want to access through browser means you can do it easily using Apache(web server) which is preinstalled in mac and host something there with plain html page or with simple php which is also preinstalled in mac.

Related

I can not run Windows apps without Internet

My work computer doesn't have a network connection.
But I need to install specific appxs.
I installed Windows Terminal from .msixbundle file.
I installed Ubuntu 20.04 (WSL distro) from .appx file.
They were downloaded and moved to my pc from another pc with internet connection.
When I run one of them an error occurs:
We want to make sure this is you. User interaction is required for authentication.
Or
The network location cannot be reached. For information about network troubleshooting, see Windows Help.
What does it mean? What do I need to do in order to run those apps without internet connection?

Accessing Meteor local web server from another local device on Mac 10.8

I am working on a Meteor website and conveniently, it will run on localhost with the simple command, meteor. However, I want to be able to access this website from other computers on the local network. The main reason I want to do this is for viewing and testing the app on mobile.
I am running Mac Mountain Lion 10.8, and they got rid of some of the convenient Personal Web Sharing pref panes. Everything else I have seen online deals with setting up your own server, but all I want to do is grant access from other local device...
Thanks
Find out your ip address 192.168.1.12 (mac system prefs/network)
start meteor in your project on a port (default 3000)
from another comp on network, browse 192.168.1.12:3000

What could prevent a custom url scheme from being registered in the Launch Services Database

I have developed a software that launches from a custom url scheme (something like "myapp://123"). It works on two of my test Mac machines (running 10.7.3 and 10.8 respectively) but somehow it doesn't work on another machine running 10.7.3
Are there any system or security settings that disable custom url scheme, or anyway I could troubleshoot this problem? It seems not to be just a faulty launch service database setting as three Macs at the client side aren't unable to register the custom url scheme.
Turns out that the client's computer is running a version of Mac OS that is too low for the developed application. I guess step 1 is troubleshooting this problem is to make sure the application can run in the first place!

How can I share a local Subversion repository between a Mac workstation and a Windows virtual machine?

I would like to share a Subversion repository between my main computer running OS X Lion and a virtual machine running Windows 7 hosted in this computer (via VMware). I am unsure what is the best way to go about this.
I am thinking of setting up Apache and Subversion server on the OS X side and hopefully that would allow my virtual to access the repository from the Windows virtual using something like Tortoise SVN and accessing the repository at http://macHostName/pathToRepository. This seems feasible since the OS X side is always running.
An alternative could be setting up Apache and Subversion on the Windows virtual, which would require me to run the virtual everytime I want to access the repository from the OS X side. Perhaps Subversion can be set up in IIS? That would save some time if I don't need to install Apache.
Either way, I am unsure of the best way to go about this set up and what the caveats of each option are. I also haven't found a good walkthrough that will show how to set up a Subversion server on any OS using Apache.
Then, there is also the option of using svnserve, which I am unfamiliar with. Will a repository not served by an HTTP server like Apache be accessible for whoever is not serving it from the OS X host and the Windows virtual?
Any pointers will be appreciated.
Both Apache and svnserve are using network protocols, so the basic network setup between your host and your guest regarding routing and firewalls will be the same.
If you already have Apache installed and are familiar to it, I recommend to use it. Otherwise my recommendation is svnserve, because it is much simpler to setup and configure. The SVN-Book has a chapter for setting up svnserve both in Windows and in OSX.

Running XAMPP on Windows through VMWare Fusion on a MAC, how do I configure apache to use my shared folders (Z:) as the web root?

Environment:
Main platform: MAC OSX 10.6
Secondary platform via VMWare Fusion: Windows 7 64-bit
Background: I'm running MAMP Pro on the MAC side with a webroot at "/www". I need to test websites in IE thus requiring a Windows installation. I installed XAMPP on my Windows side and changed the apache root directory to "Z:\www", the location of my MAMP webroot which is a shared folder between MAC and Windows.
When I try to access a local site from windows (http://localhost/asite) I get a 403 Forbidden error:
Access forbidden!
You don't have permission to access the requested object. It is either read-protected or not readable by the server.
If you think this is a server error, please contact the webmaster.
Error 403
localhost
07/30/10 14:21:07
Apache/2.2.14 (Win32) DAV/2 mod_ssl/2.2.14 OpenSSL/0.9.8l mod_autoindex_color PHP/5.3.1
What other configuration changes need to be made for this to work if it will work at all?
Thanks,
Chris
Thanks to those who responded. I did a little research on the types of network connections and here's how I resolved the issue without using XAMPP at all.
To recap, I'm running Win7 on my Mac via VMWare Fusion as a virtual machine. I have MAMP running a local web server on my Mac with a webroot at /www and I want to be able to also access the web server from browsers in Windows.
In short, I want to be able to go to http://localhost/mysite from Safari (Mac) or IE (Windows).
Changed my Fusion Network Adapter to Bridged, since I am working from a home office.
Refreshed my network connections using the ipconfig commands in the command prompt.
Edited my windows hosts file to reflect: 192.168.1.102 localhost
Done and done.
I hope someone else can find this useful.
Chris
Is there any specific reason you're trying to serve your site from XAMPP, rather than just MAMP? I worked in a similar environment a couple of years ago, and I simply set the virtual machine's networking type to NAT (so that the guest has a different IP from the host), and then pointed IE at the IP address of the host running MAMP.
Maybe I didn't quite understand your problem completely, but:
"I need to test websites in IE"
you don't need to setup a Web server to do that...
Keep using Apache on your Mac host and point IE from your Windows VM to the host machine IP, as peterjmag suggested.
Also, wasn't there a Mac version of IE?
Again, my apologies if i misunderstood you - I don't want to sound arrogant;)
"Z:\www ... a shared folder between MAC and Windows"
What's this - a network share? Do you get the same error if you use a local folder in your VM (eg: C:\www)?
Try mounting /www from your VM - go to it's settings > options tab > shared folders. Select Always Enabled. Click Add and browse to your /www host folder. This should make /www accessible in your VM Windows.
Finally, just in case: check Windows permissions on the www folder.
Hope that helps!

Resources