I have a next.js app on Now and I'm adding the ability for users to point domains at their account. Kinda like about.me.
What's the best way to approach this? I've done this in Rails in the past but not sure how to do it here.
Thanks!
The best way would be to do the following:
Use the ZEIT API to programmatically add domains.
If you are going for over 50 domains, make sure you know the limits of your account. Having too many domains will require an enterprise plan. Take a look at this documentation.
If you are launching a business, a good support plan will help you get started with the API quickly. Again, take a look at Enterprising offerings if possible.
Reach out to support#zeit.co for any needed information.
How do I allow a normal gmail user access to use on the Google App Maker apps I've made. Is this possible ?
If you have to have a separate gsuite account for each user using the app then how viable is it ?
Anyway any help would be much appreciated.
Many thanks
Samuel
I know this is an old question, but I just spent too much time to get the answer.
So here there is google's answer:
Can I share my apps with users outside my organization?
No. Only users in your G Suite organization can use your app. For some apps,
you can work around this limitation by using Google Forms to collect
user input in Google Sheets, then import the data from the sheet.
I don't think that the form "hack" is going to help a lot of people, but it's nice they mentioned it.
As I understand it, you do need a GSuite business account ($10/month/user) to use an App Maker app.
I hope that Google is not primarily doing that to make money, but to initially have a smaller number of users and apps, and use the smaller user base to shake out issues and later open it up for the general public (ie for the Firebase platform). I don't see why this would be impossible or even difficult, but of course, hope is not a strategy.
Morning/afternoon/evening all,
I am building a website for a rental property in France and the client wants to be able to use a single solution to manage bookings across the following platforms: Booking.com, AirBNB, Abritel (French) and Gites de France. Ideally, with the possibility of integrating TripAdvisor later.
So, when the centralised platform is updated, it updates across all the other platforms automatically. And when a booking is made, it feeds through to the centralised system.
I am highly doubtful that this one-shop solution exists but thought I would ask anyway. If it doesn't exist, would a bespoke solution be possible? Any other suggestions welcome.
Thank you
EDIT: I have learned that websites such as AirBnb can sync with iCal and Google Calendar. I wonder if this could be a simpler solution.
its is very possible provided the third party platforms have services that can be called for data exchange..... first check for the services exposed by those platforms and how to consume them.
We're looking into implementing an issue tracker for our web agency. The problem is that most issue trackers seem to revolve around the assumption that an issue is a bug, whereas in a web agency environment, a lot of the issues (request, or whatever you want to call them) are about changes and additions to a current web site.
It also seems to me that a lot of issue trackers assume that you're working on one main software project, and uses that project as the focus of the tracker. A good issue tracker for a web agency would be one which puts each separate client and their issues at the heart of the system, making it easy for them to track and report issues.
Does anyone know of a good issue tracker for the web agency workflow? What are other people using?
In my experience, issue trackers are so closely coupled to the workflow of the organisation that what works in one place may be a complete misfit in another. That said, could basecamp work for you?
We are using Gemini very flexible with the ability to have workflow at the project level.
But where Gemini really helps us is the cross project views. You can view your work across all projects with really good fitering.
Have you had a look at fixx at all? Obviously, being the developer of fixx, I will want to plug it but I know from first-hand experience that a lot of our customers are web agencies who work in a service-oriented environment and need to track more than just "software development" projects.
With fixx, you can define custom issue types (for example "change request" or "Copy changes") and track work against that type.
Unfortunately, fixx still does suffer from the "project-centric" view but a lot of our customers work around this by defining a project per client/website. So, if you were doing web/maintenance on stackoverflow.com, you would have a project called "stackoverflow.com maintenance" and would assign all your users from that company to that specific project. From there, using notifications and filters, it would be very easy for clients to keep track of progress on their specific issues.
FogBugz – it's simple by default, but extensible; it's got an integrated wiki, charts, tags, and you can even tie it to your source-control system (and they also offer their own integrated source control system, Kiln, which is pretty amazing with FogBugz).
Are you using other applications to manage the rest of your business' operations?
I ask because WORKetc has great issue tracking software, and this software is combined with other aspects of business management which can simplify the management process. So not only could you manage all support inquiries and responses in one place, but also your projects, finances, and contacts. Most importantly, it would allow you to use one central contact base for your entire company, while allowing you to reference that contact information (as well as lead information) while working on support inquiries, projects, invoices, etc.
WORKetc's support system works around email integration and simple ticket system (as well as prioritizing) and directly integrates with projects, contacts, and other aspects of the system so that you can save time while responding and managing tickets.
I think especially for the use case of a web-agency, where it's not really about bugs, but mostly (visual) feedback and all of it happens on the web, a visual feedback tool might be the thing you're looking for. Most of these tools will create a screenshot of the webpage and include the given feedback on it.
Some of them also have some kind of dashboard where you can discuss further, or have integrations to other tools like Basecamp (and some them do both).
Here's an article from smashing magazine, which describes a lot of them, e.g.: TrackDuck, BugMuncher. Another great tool the article doesn't mention, maybe because the article is a bit dated, is Usersnap – this one even includes browser extensions.
Planning to start a small aggregator for a personal project, so far I have a few inquiries on gathering information for the site. I'm still clueless on where to begin. what kind of infrastructure do i need? where do i get the feeds and can I sort them out depending on the theme of the info requested?
any feedback is appreciated. thanks
This is a pretty open-ended question, but here's where I'd start:
Technology for handling feeds -- WCF Syndication. Also, read and understand the RSS and Atom specs.
Infrastructure -- depends on your situation. Is it just for you, or a few friends or are you talking about building the next Google Reader? If it's smaller-scale, then look at a hosting solutions like GoDaddy, DiscountASP.NET, etc. (There's hundreds of them.) If you're talking a larger-scale type of solution, look at hosting it in the cloud - Rackspace, Amazon, Windows Azure.
Where do you get feeds? Pretty much anywhere. Personally, if this site is for other users, let the users enter them in (why be in the business of trying to guess what feeds people would want to subscribe to?).
I think you need to provide more requirements in order to get more solid feedback. Start with looking at WCF Syndication and get a feel for that library in terms of how to programmatically handle RSS and ATOM feeds (both subscribing and publishing). Once you understand that, I think you'll have a better handle on your next steps.
Hope this helps.