I have a Box.net (.com) account and wanted to create an application in Box.
I looked around the admin pages but can't find it.
I know it is possible, but I can't find it in the Administrative application pages. Where can I find it?
The "development interface" for Box is not in the administrative pages. You have to create a separate account for development. IMHO this is limiting, since most likely companies will have development teams and they should be linked to the Admin account, but I understand that separating them brings more flexibility.
But I digress. The admin pages are reached through https://box.com, but the development pages are in https://developers.box.com/
Related
I'm new to coding, quite obviously. I created a web design using HTML in Adobe brackets. How do I create my own website from here? Like getting a domain or host. Not sure if those are even the right words to use
Welcome to the wonderful world of web development! Congrats on making your first HTML site.
I am not sure how much you know about the topic, so I will try to explain the basics of getting a site "online".
Websites essentially allow you to access other people's HTML documents in a file directory. You have probably noticed some URLs in the form "www.example.com/file.html". This means that to get your site online, you will need a computer to "host" your HTML files from. Since you probably don't want to leave your computer on 24/7, you will need to use a web hosting service. There are loads of web hosting companies that offer similar services, but they all have the same goal essentially - providing the means for people to remotely access your files. My hosting service of choice is Digital Ocean because they offer a decent price on a small web server. Through your web server (which is essentially a computer running Linux in a warehouse somewhere), you can install web server software (like Apache) which will allow you place your html files into a special directory which will can be accessed from a web browser (something like /var/www/html). Once your files are uploaded to your server, you can access your website through your server's IP address (some esoteric number in the form of http://xxx.xxx.xxx.xxx).
Of course, you don't access websites through an IP address (at least most humans don't). This is where a "domain name" comes in. The web provides a nifty feature (DNS) which allows you to map a domain name to an IP address. So you can go to your favorite domain purchasing website (something like GoDaddy, which you have probably heard of) and purchase an open domain name of choice. Once you purchase the domain (something like DragonFire09.com), you can map this domain name to your web server's IP address.
These are the two main steps to getting a site online! I hope this provides some insight. Note that getting a website online costs money because you need to pay for a hosting service and a domain, however its a great experience because along the way you will get your hands dirty with Linux and other parts of the web stack.
Of course, you can always create files locally and test them through your own web browser free of charge.
Good luck!
The question is pretty clear I think, but I will elaborate on why I'm asking it.
I created a little blog engine based on OneNote. Basically, the blog configuration asks for an access to OneNote. Then the user chooses a section under which the blog posts are stored.
There is a cron script that will use all these informations to automatically get new pages, fetch the medias and cache every, and finally display the posts.
I chose OneNote because I own three Windows 8 computers and a Windows Phone, so OneNote was an easy choice, as I didn't want to get an other application to manage my blog.
There is still a lot to do (as always with softwares...), but I want to make this more or less an open source project, so that other people can install it on their websites and link it directely to OneNote.
The only "big" obstacle for this now is that authentication in the OneNote API needs to register the application on the Live Connect, and specify a redirect domain. So every user wishing to use this blog engine on their server will have to register their own application... That will look complicated just for a blog, especially if you're not tech-savvy.
Is there a way to "skip" or work around this requirement, even if it requires the user to make the section public (as it is for a blog, this doesn't seem too much to ask) ?
Thank you in advance,
Cheers
Sounds like an awesome project! When you get it released be sure to let us know at #OneNoteDev.
Unfortunately, at this time there's no way to circumvent the requirement for Live Connect OAuth configuration. You could offer a hosted variant so only you need to worry about the LiveID configuration.
I currently have a developer account setup in box and looking for steps to move it to production. I cannot find details on
If there is number of users allowed
How to turn production mode on
I am have setup initial account with auth redirect url. Configured my app key and token in my web application.
In terms of "productizing" I've heard a few different ways this term
1) To just make an app generally useable among consumers of the third party app, all that is needed is a functional integration with Box APIs. Assuming that you have implemented oAuth correctly and integrated our APIs functionally, there is no barrier to everyday users to using that integration between Box + third party app.
2) To make an app available to Box users ("productionalize" is a term I hear often), the best way to do this is through our gallery. Developers can follow these instructions for creating a listing in our App Gallery: cloud.box.com/appgallerylisting
I am developing a login and account system for use with an existing website, this will run on a subdomain under the main site url.
I would like to use a subdomain that is generic enough so it isn't tied to an account system but not off-putting to users.
I was thinking of www2 but I am concerned people will see this and think its not "legitimate".
Thanks
Some more context.
The new site is currently used for the login and account system but I will eventually migrate the whole website to the new system, this means the services and pages served by the subdomain will very a lot so it can't be specific to one thing.
Try something generic in the interest / knowledge domain of the existing website. What does the existing website do or provide? This can help you determine a proper subdomain.
Some generic examples:
info.domain.com
account.domain.com
auth.domain.com
app.domain.com
to.domain.com
Providing a better subdomain is going to require some more context.
I need advice.
I inherited a website that's been around a long time. The website gets a lot of organic traffic from Google. The business and website owner is upgrading the site to make the content more manageable. At the moment, a wordpress CMS powers half the site. Physical html pages make up the remainder of the site. Here's a summary:
1) Guide section which consists of a php wordpress driven blog found at http://mysite.com/guide. Individual pages in the guide section have urls such as http://mysite.com/guide/4930-hello-world or http://mysite.com/guide/489-welcome-to-my-site. The business owner spent 2 months populating these pages and is reluctant to scrap it for another system.
2) E-commerce section which consists of a thousand static/physical product pages. The product pages are NOT dynamically driven and no url rewrite rules are involved. The pages have urls such as http://mysite.com/products/239123-sofa.html and http://mysite.com/products/23-office-desks.html
The owner wants to use a non-PHP ERP or CRM solutions to power the website's e-commerce section and streamline some of the business' accounting, inventory, marketing and work-flow operations.
I have never worked with ERPs or CRMs before. Some questions I have are:
1) Is it a good idea to have one website under one domain driven by two different technologies? Wordpress manages pages such as http://mysite.com/guide/4930-hello-world while a Microsoft application manages pages such as http://mysite.com/products/239123-sofa.html. As mentioned earlier, the business owner is reluctant to scrap wordpress because he put considerable effort into populating it.
2) What challenges will I experience implementing url-rewrite rules (because it's two technologies under one domain, but different sub-directories)? I need to make sure the website retains its Page Rank and SEO goodies.
3) What server configuration challanges will I experience?
I've never replaced a legacy system of this magnitude on my own before. I appreciate any advice or feedback you guys can offer. Also let me know if there's anything else I should research.
Thanks
You can think of a configuration where you have separate logical/physical back-end servers for each system. Then you can have a front-end proxy (for instance Apache with mod_proxy) serving all the requests and separating them between the different back-ends.
This will also work as an application level "firewall" protecting you from unwanted requests, since you will only forward URLs that you recognize.
With regards to #1:
Big picture, while it's tough to say with the level of detail you've specified I'd say you'll probably want to make the system homogenous: use one technology and permanently redirect the legacy pages. It'll be much more cost-effective to maintain. Port the legacy WordPress content over to a new, single system.
With regards to #2:
If you're using ASP.NET, you can write an implementation if IHttpHandler to do the URL redirection, issuing an HTTP 301 (permanently moved) so that Google knows where the content has been moved to. I'd imagine other technologies have similar capabilities.
With regards to #3:
If you're using a single technology, this issue should be alleviated.