Can I request a docker-compose setup for development? I don't have Go installed in my machine.

Originally posted by @lxcid in #6 (comment)

Dependent on #21 and #22

Up for discussion

• Use hosted solution like https://www.algolia.com
• Using existing database capability (e.g. postgresql)
• Using specialise database like Elasticsearch

URL: /posts/new

Deployed the latest code to dev.jobsgowhere.com

However, it fails to fetch the response as the URL is hardcoded to the localhost.

Replace this to point the hardcoded URL to HOST_URL

From #1

Should be assigned to @kajalsinha

From #1

Should be assigned to @SheldonCheng and Yao Long

• Talent API currently not returning all results and missing the offset and limit params.

There's a few authentication mechanisms that I can think of to support:

1. Our own signup/login
2. LinkedIn https://docs.microsoft.com/en-us/linkedin/consumer/integrations/self-serve/sign-in-with-linkedin?context=linkedin/consumer/context
3. Google Sign-in https://developers.google.com/identity/sign-in/web/sign-in

LinkedIn

Pros

1. ability to load work profile for job seekers
2. ability to load company profile for job posters

Cons

1. user base needs to have LinkedIn account

Google

Pros

1. more likely to have a gmail account for most user base

Cons

1. not much information to pre-populate other than email address

Would we want to only help users with LinkedIn account? Older non tech savvy folks might not have LinkedIn account, but then again they might not even use our app.

Test

The current site is not using SSL certificate. We can use let's encrypt which is free.

Related article.

• https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/SSL-on-amazon-linux-2.html
• https://medium.com/@gnowland/deploying-lets-encrypt-on-an-amazon-linux-ami-ec2-instance-f8e2e8f4fc1f

The ones that we have in place right might not work for us.
I think it might make sense to use labels to prioritize issues as well.

• Style inner text content
• Favourite button

• meta tags
• content for crawling

Issue to check slack integration.

• Create table for Job and dependencies
• Integrate with SQLBoiler
• Generate models
• Create service
• create endpoint for the APIs

!util.Contains(ctx.Request.Header["Content-Type"], "application/json") {

https://github.com/jobsgowhere/jobsgowhere/blob/master/main.go#L47

Could refer to https://www.prestonlamb.com/blog/creating-a-docker-image-with-github-actions for reference

From #1

Should be assigned to @lxcid and @SheldonCheng

Action Items

• Find out whether you want to use React / Next.js or both with golang backend (@lxcid and @SheldonCheng to discuss)
  • @SheldonCheng: for integration with golang, it shoudln't be too different from react i think.
    it can be built into static html and served, just that initial api calls and page rendering happens on server
    don't think we will have a lot of static pages so perhaps no great advantage to using nextjs here (other than SEO maybe). So prob can just use standard react
• TypeScript or JavaScript
  • TypeScript, learning experience for implementors

I was thinking of creating a basic table structure which should be strong enough to get started. This is just the beginning so foreign key references are not mapped. I want to design it in a way that in future it can be broken down to micro services by feature i.e. set of related features can be grouped in one micro service.

Please suggest changes/thoughts. Thanks!

-- Add your release scripts here
CREATE TABLE person
(
    id           UUID PRIMARY KEY,
    iam_id       TEXT      NOT NULL UNIQUE,
    dp_url       TEXT,
    email        TEXT      NOT NULL,
    iam_provider TEXT      NOT NULL,
    created_at   TIMESTAMP NOT NULL,
    CONSTRAINT UNIQUE (email, iam_provider)
);

CREATE TABLE job
(
    id          UUID PRIMARY KEY,
    title       TEXT      NOT NULL,
    description TEXT      NOT NULL,
    location    TEXT      NOT NULL,
    created_by  TEXT      NOT NULL,
    created_at  TIMESTAMP NOT NULL
);

CREATE TABLE skill
(
    id          UUID PRIMARY KEY,
    title       TEXT UNIQUE NOT NULL,
    description TEXT
);


CREATE TABLE related_skills (
    -- todo
)

CREATE TABLE job_skill_map
(
    job_id   UUID NOT NULL,
    skill_id UUID NOT NULL,
    required BOOL DEFAULT FALSE,
);

CREATE TABLE job_seeker
(
    person_id       UUID PRIMARY KEY,
    title           TEXT      NOT NULL,
    current_company TEXT,
    created_at      TIMESTAMP NOT NULL
);

CREATE TABLE job_provider
(
    person_id       UUID PRIMARY KEY,
    title           TEXT      NOT NULL,
    current_company TEXT      NOT NULL,
    created_at      TIMESTAMP NOT NULL
);

API URL

http://dev.jobsgowhere.com/api/sendmessage

Header

Set the authorization header

Body

{
	"from": "<id_of_sender>", 
	"to": "<id_of_receiver>", 
	"subject": "<message_subject>", 
	"body": "<message_body>"
}

Check #76 for reference.

Could use https://github.com/coord-e/magicpak

From Yao Long in #general 17/6

<!-- Google Tag Manager -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window,document,'script','dataLayer','GTM-NNN3PVC');</script>
<!-- End Google Tag Manager -->

<!-- Google Tag Manager (noscript) -->
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-NNN3PVC"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager (noscript) -->

Database migrations are needed for adding new database objects in correct order.

Change the structure of API.

From #1

Should be assigned to @subhransu